Hello all, for a few weeks/months now, my computer has stopped going into suspend mode. Here is what happens when putting it to sleep (using GNOME’s power menu) or using systemctl suspend:
- Display turns off, peripherals turn off (keyboard lights off etc), fans spin up before sleep as usual
- Fans go back to idle speed, computer stays on
- Have to press the keyboard, wake the display up and go in the power menu again to suspend it (from the lock screen), and it works every time like this.
I have no idea what could be preventing suspend and what I could find online did not really help a lot. I don’t think it is a USB device because I tried unplugging most of them except my mouse or my keyboard and it still did not work, and the second time on the lock screen it always suspends like intended
- Distro: Fedora 40
- DE: Gnome 46
- GPU: NVIDIA GTX 1080Ti (Wayland)
- CPU: Intel 10850K
- MB: Gigabyte Z590 Gaming X (everything is up to date)
thx !
I’ve had some suspend adventures too, but my experience is just on Intel laptops.
About a month ago, Debian Trixie had a regression that made my laptop wake up right after a suspend attempt. Afaict, it was not directly a kernel change, something in userland changed and triggered problems. This pm_async thing fixed it. Frankly, I don’t know why “async” power management is a thing anybody would want. Taking a whole extra millisecond to suspend in a more reliable way seems like a no-brainer.
echo 1 > /sys/power/pm_debug_messages # why would you ever want to not syslog it??
echo 0 > /sys/power/pm_async
Cat /sys/power/pm_wakeup_irq may tell you something about whomst is responsible for sleep failure. Anyways, suspend is the worst thing to diagnose good luck.
