Linux 6.19.4 regression may cause failure to suspend properly on certain AMD hardware
Posted by anh0516@reddit | linux | View on Reddit | 13 comments
anh0516@reddit (OP)
It's already fixed, staged for 6.19.6. I encountered the same problem on an IdeaPad 5 2-in-1 14AHP9 - Type 83DR.
gazpitchy@reddit
Still getting it here
anh0516@reddit (OP)
What kernel version? Make a bug report of your own.
SelectionDue4287@reddit
More recently added sleep states, active power management, smarter CPU power management and suspend are all really error prone, needing delicate balance and good implementation in OS, firmware and hardware.
It's not uncommon for me to find PCs which experience weird lockups, crashes or reboots, which cease after turning all of those off. You do need those on mobile devices and laptops though...
Bubbly_Extreme4986@reddit
Anyone else just disable hibernation/sleep on their main machines?
anh0516@reddit (OP)
No, because I want to immediately resume what I was doing.
S1rTerra@reddit
I just don't want to wait for a reboot and if I really need to restart, I'll just sign out and sign back in. Fixes most stuff a reboot would besides a couple of minor things
Synthetic451@reddit
Hmm I am getting that
amd_pmc AMDI0007:00: Last suspend didn't reach deepest stateerror on my Asus Flow Z13 on 6.18.13. Anyone know if this regression also hit the 6.18 series?anh0516@reddit (OP)
You mean 6.18.14? https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.14 contains the commit, so it shouldn't happen on 6.18.13.
You should reply to the email chain letting them know.
Synthetic451@reddit
Interesting, 6.18.14 hasn't landed in Arch yet so I am definitely on 6.18.13
anh0516@reddit (OP)
You should bisect if you know how, on the linux-stable 6.18.y branch. Once you've found the problematic commit, you can participate in the conversation.
If you don't know how to bisect, it's still worth saying something, though.
Rockytriton@reddit
* cries in nvidia drivers... *
anh0516@reddit (OP)
This isn't about GPUs.