linux-kernel - [REGRESSION] bluetooth: mt7921: Crash on Resume From Suspend And Hibernate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241127231432.8112-1-jglotzer@gmail.com>
Date: Wed, 27 Nov 2024 15:14:32 -0800
From: John Glotzer <jglotzer@...il.com>
To: regressions@...mhuis.info
Cc: Aaron.Hou@...iatek.com,
	Chris.Lu@...iatek.com,
	Deren.Wu@...iatek.com,
	Hao.Qin@...iatek.com,
	Sean.Wang@...iatek.com,
	johan.hedberg@...il.com,
	linux-bluetooth@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux-mediatek@...ts.infradead.org,
	luiz.dentz@...il.com,
	marc.payne@...sys.co.uk,
	marcel@...tmann.org,
	regressions@...ts.linux.dev,
	steve.lee@...iatek.com,
	tiwai@...e.de
Subject: [REGRESSION] bluetooth: mt7921: Crash on Resume From Suspend And Hibernate

I've been following this thread since hitting this issue on my AMD Ryzen 5 7600.

People have reported being able to mitigate by either turning off Bluetooth in system settings
or by using a systemd sleep script like the one below (this is the approach I've taken,
it works fine.)

cat /usr/lib/systemd/system-sleep/sleep-fix.sh
#!/usr/bin/env bash
case ${1} in
    pre)
    rfkill block all
    echo "Killed wifi/bluetooth"
    ;;
    post)
    rfkill unblock all
    echo "Started wifi/bluetooth"
    ;;
esac

In following the related email threads it seems that this particular email thread has
not had any activity since 10/21/2024. Now the focus seems to be on firmware download which
in my admittedly non-expert opinion seems to be not clearly related.

There are multiple reports of this issue on various user forums (Fedora, Arch, Redhat, others)
but it seems that we've lost focus on the kernel side on addressing this regression.

Thanks all.