rotopenguin , 2 days ago

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.