You are not logged in.
Hi everyone,
I'm moving over from Windows to Linux before I have to switch to Windows 11, so this is a fresh install. I was having an issue with S3 power management mode aka suspend to RAM aka s2r aka deep sleep aka a half a dozen other names you may find while searching. Updating my BIOS fixed the problem. I spent about 12 hours figuring that out and I figured I'd try to save some others the hassle, since this seems to be a fairly common issue and I only found the solution hinted at on a Redhat forum.
ISSUE:
Suspending computer to RAM seems to work successfully (according to journalctl and dmesg) producing a powered down state, but when pressing keyboard inputs to wake the computer from sleep, the system reboots instead of returning to original state. The computer DOESN'T immediately reboot when going into sleep , it correctly waits for keyboard inputs.
Sleep works fine on Windows.
Running on
Boot media that only contains Arch Linux, no other Linux or Windows partitions.
UEFI system, not legacy
CSM disabled in BIOS
AMD Ryzen CPU
NVIDIA GPU
Kernel 5.17.9-arch1-1
KDE Plasma X11
dmesg/journalctl reports logs similar to below with no obvious errors or failures (even with more verbose logs)
May 21 08:33:08 COMPNAME systemd-sleep[1451]: Entering sleep state 'suspend'...
May 21 08:33:08 COMPNAME kernel: PM: suspend entry (deep)
-- Boot (hex values) --
(Normal Boot Process)
SOLUTION:
My BIOS were about 3 years out of date. Updating allowed the computer to correctly wake from deep sleep state.
Other Info scattered around while searching for this:
Diagnostic methods https://01.org/blogs/rzhang/2015/best-p … ate-issues
How to change kernel parameters in order to USE those diagnostic methods https://wiki.archlinux.org/title/Kernel_parameters
S3 power state does NOT use swap space (described in the link below, but a common question)
Information on power management https://wiki.archlinux.org/title/Power_ … _hibernate
The Systemd section has links to scripts that will run before and after suspend/resume processes, but they are NOT responsible (to my knowledge) for running those processes (minor confusion I had)
Some of this is obvious/common information, but it was a little scattered or hard to track down.
Hopefully this helps, most of the posts I found on google trail off without a solution and I don't remember seeing anything about BIOS while searching specifically for Arch Linux (it might be on the wiki and I missed it).
Last edited by LostintheBinarySea (2022-05-21 16:41:05)
Offline