FS#75603 - [linux] Kernel 5.19.1 breaks suspend

Attached to Project: Arch Linux
Opened by UrbenLegend (UrbenLegend) - Sunday, 14 August 2022, 18:36 GMT
Last edited by Toolybird (Toolybird) - Thursday, 18 August 2022, 22:50 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Updated to kernel 5.19.1 today and noticed that suspend is broken. The system seems to go to sleep fine, but attempting to wake it up immediately causes a full forced shutdown.

System specs:
Linux 5.19.1.arch2-1
AMD Ryzen 3900x on a Asrock Taichi X570
Nvidia RTX 3090

Steps to reproduce:
1. Update to kernel 5.19.1
2. Suspend the machine
3. Attempt to resume.
4. Notice that the system shuts down immediately
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 18 August 2022, 22:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  linux 5.19.2.arch1-1
Comment by Toolybird (Toolybird) - Monday, 15 August 2022, 06:51 GMT
The symptoms described here [1] look suspiciously similar. Seeing as it's a regression, you could always put that 3900x to good use and perform a bisection :) Otherwise, you'll have to do some debugging [2][3].

[1] https://lore.kernel.org/all/YvLJ9TQeXP%2FmiUgT%40hatter.bewilderbeest.net/
[2] https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate#Troubleshooting
[3] https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html
Comment by loqs (loqs) - Wednesday, 17 August 2022, 22:46 GMT
The fix for the nct9772 issues was in 5.19.2 [1] currently in testing. Does that resolve the issue?
If not there are some bisection kernels your can try in [2].

[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a9fba9f20dc9c1da01e3b72fb109f3ef6d59ee84
[2] https://bbs.archlinux.org/viewtopic.php?pid=2052198#p2052198
Comment by UrbenLegend (UrbenLegend) - Thursday, 18 August 2022, 04:18 GMT
Just tested with 5.19.2 from testing and it seems to resolve it! Thanks so much for locating the upstream bug and packaging the fix so quickly!

Loading...