linux-kernel - Re: [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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1eeecc68-be5f-46e6-aed6-594c4b32df21@gmail.com>
Date: Sat, 21 Dec 2024 10:52:54 +0100
From: Sergio Callegari <sergio.callegari@...il.com>
To: jglotzer@...il.com
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@...mhuis.info,
 regressions@...ts.linux.dev, steve.lee@...iatek.com, tiwai@...e.de
Subject: Re: [REGRESSION] bluetooth: mt7921: Crash on Resume From Suspend And
 Hibernate


On 06/12/2024 03:29, John Glotzer wrote:
 > Sergio,
 >
 > My apologies, I neglected to mention that my setup is PCI, and not USB.
 >
Thanks for confirming, good to see that the issue can be reliably 
reproduced with a setup similar to mine!

 >
 > What I am struggling to understand is given how easy this issue is to 
reproduce -  an AMD CPU, Mediatek MT7922 wifi/bluetooth chip,
 > and a 6.11 kernel, you suspend, and then wake up, kernel panics -  I 
would have thought that the interested parties would
 > make this a priority.
 >
I wonder it it might be possible to revert back to the code in kernel 
6.10 (that worked fine), until the current issue can be triaged and fixed.

The other way round, I am getting the impression that other changes are 
getting stacked on top of the faulty ones, further complicating the picture.

As of today, with kernel 6.11.11, the issue has /worsened/ for me. On 
6.11.4 I could hibernate/resume by kfkilling bluetooth only, which was 
not so bad, since I only use bluetooth rarely. With 6.11.11 I need to 
rfkill the wlan too.

Can this be confirmed too?

Sergio