There is a nasty regression wrt mt7921e in the last LTS series (6.12). If your computer crashes or fails to get out of hibernation, then at the next boot the mt7921e wifi does not work, with dmesg reporting that it is unable to change power state from d3cold to d0.
The issue is nasty, because rebooting won't help.
The only solution that I have found to the issue is booting a 6.6 kernel. With that the wife gets alive again. If, at this point, you boot into 6.12, everything seems to be fine again, until a boot fails and from that moment on you are without wifi.
Working around the issue is not very discoverable. On my machine not even a hardware reset (40s of power off button pressed) helped alone, without going through the 6.6 kernel boot.
I think the regression was introduced with 6.12 and I remember having no issues with previous kernels, but cannot be 100% sure.
Similarly, I do not know if the bug is with the wifi card driver itself or with something related to PM or PCIe.
The machine on which I am experiencing the issue is an Asus ROG 14 laptop (2022 edition), with AMD CPU and GPU.
Thanks for the attention, Sergio
On Wed, Mar 19, 2025 at 08:38:52PM +0100, Sergio Callegari wrote:
There is a nasty regression wrt mt7921e in the last LTS series (6.12). If your computer crashes or fails to get out of hibernation, then at the next boot the mt7921e wifi does not work, with dmesg reporting that it is unable to change power state from d3cold to d0.
The issue is nasty, because rebooting won't help.
Can you do a 'git bisect' to track down the issue? Also, maybe letting the network driver authors know about this would be good.
thanks,
greg k-h
Might be able to test on the distro built kernels that basically trace the releases and stable point releases. This should start helping bracketing the problem a bit better as a starter. But it is going to take a lot of time, since the issue happens when the machine fails to get out of hibernation, that is not always, and obvioulsy I need to try avoiding this situation as much as possible.
Incidentally, the machine seems to hibernate-resume just fine. It is when I suspend-then-hibernate that I get the failures.
Before contacting the network driver authors, I just wanted to query whether the issue is likely in it or in the power-management or pcie subsystems.
Thanks, Sergio
On 20/03/2025 00:54, Greg KH wrote:
On Wed, Mar 19, 2025 at 08:38:52PM +0100, Sergio Callegari wrote:
There is a nasty regression wrt mt7921e in the last LTS series (6.12). If your computer crashes or fails to get out of hibernation, then at the next boot the mt7921e wifi does not work, with dmesg reporting that it is unable to change power state from d3cold to d0.
The issue is nasty, because rebooting won't help.
Can you do a 'git bisect' to track down the issue? Also, maybe letting the network driver authors know about this would be good.
thanks,
greg k-h
Hey Sergio,
On 25/03/20 08:49AM, Sergio Callegari wrote:
Might be able to test on the distro built kernels that basically trace the releases and stable point releases. This should start helping bracketing the problem a bit better as a starter. But it is going to take a lot of time, since the issue happens when the machine fails to get out of hibernation, that is not always, and obvioulsy I need to try avoiding this situation as much as possible.
Which linux distro are you using? If you're on Arch Linux I can provide you with prebuilt images for the bisection :)
Incidentally, the machine seems to hibernate-resume just fine. It is when I suspend-then-hibernate that I get the failures.
Before contacting the network driver authors, I just wanted to query whether the issue is likely in it or in the power-management or pcie subsystems.
Thanks, Sergio
Cheers, Chris
On 20/03/2025 00:54, Greg KH wrote:
On Wed, Mar 19, 2025 at 08:38:52PM +0100, Sergio Callegari wrote:
There is a nasty regression wrt mt7921e in the last LTS series (6.12). If your computer crashes or fails to get out of hibernation, then at the next boot the mt7921e wifi does not work, with dmesg reporting that it is unable to change power state from d3cold to d0.
The issue is nasty, because rebooting won't help.
Can you do a 'git bisect' to track down the issue? Also, maybe letting the network driver authors know about this would be good.
thanks,
greg k-h
linux-stable-mirror@lists.linaro.org