Dell XPS 13 (9350) laptop has been running Fedora since 2015 and never had any issues with suspend/resume. Beginning with kernel 6.2.8-200 on Fedora 37 there were frequent failures to resume after suspend. The first suspend-resume cycle after a reboot would often work, but subsequent attempts would fail. I tried to debug but without success and then did a clean install of Fedora 38. The same problem occurred with kernels 6.2.9-300 and 6.2.11-300. One successful resume with this kernel generated a call trace which is attached. However this trace does not always appear. I have installed older kernels from koji, the problem starts to appear with the first 6.2 kernel. - 6.0.0-0.rc2.20220824gitc40e8341e3b3.23 working suspend-resume - 6.1.0-0.rc8.20221209git0d1409e4ff08.62 working suspend-resume - 6.2.0-0.rc2.18 resume fails after suspend Reproducible: Sometimes Steps to Reproduce: 1. Install a kernel version >= 6.2 2. Reboot, then suspend 3. Resume is successful ~50% of the time 4. Suspend again 5. Resume is almost never successful after two suspend cycles
Created attachment 1959804 [details] Call trace after successful resume
Dell XPS 15 has precisely the same issue. The only difference is that I see the error almost every time I try to resume. It happens for both s2idle and deep suspend. My reproducibility is almost 90%. Never two resumes within a day. I'm looking for a workaround, so far the below didn't help - disable Bluetooth in BIOS - switch to Nouveau - switch to proprietary Nvidia drivers - change s2idle -> deep Steps to Reproduce and my observations: - Suspend - Wait a longer period (~1h) - Press the keyboard on the laptop (nothing) - Press the power button (nothing) - Press many keys a couple of times (nothing, black screen) - After 30 seconds of pressing keys, the CPU goes 100%, the laptop becomes very loud, like in some kind of intensive computation loop, and the whole laptop increases hot very quickly. All monitors stay off. I restart immediately to avoid overheating. - It feels like the longer I wait on suspend, the less likely I will be able to resume. My specific setup which may affect the increase in reproducibility: - 2 external monitors, 64GB RAM. In previous Fedora/kernels s2idle worked fine, deep never. Now, deep works sometimes, but s2idle fails in 90% of cases.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.