You are not logged in.
Since upgrading to kernel 5.18.7, suspend to RAM stopped working. Hibernate still works fine.
Looking in the systemd logs, I see that systemd-susped fails to write to /sys/power/state, although the file certainly exists when the system is running, and contains "freeze mem disk".
Trying
echo mem > /sys/power/stateI get the same result: the screen goes momentarily black, then wakes up again, and the console has an error "/sys/power/state: No such file or directory".
Hibernating works fine, though, both through systemd and with
echo disk > /sys/power/stateAny ideas?
[Update:] Upgrading to 5.18.8 solved the issue.
[Update:] Or maybe not. It seems to happen randomly.
[Update:] I have updated to 5.18.9, but still have the same problem, intermittently.
Last edited by defeo (2022-07-07 21:49:10)
Offline
- Try to suspend using
systemctl suspend and grab a journal afterwards + share it here.
- Does suspending work if you use the LTS kernel?
- Disable Bluetooth before suspending. Does it work now?
- Unplug all external devices before suspending. Does it work now?
Offline
Thanks for your answer. Upgrading to 5.18.8 solved the issue. Marking the thread as solved.
Offline
Hmmm... the issue may not have been solved, after all.
It seems that the first few times after boot suspend works fine, but then it stops working. Here's the output from systemd-suspend
Jul 07 23:46:59 merry systemd[1]: systemd-suspend.service: Changed failed -> start
Jul 07 23:46:59 merry systemd[1]: Starting System Suspend...
Jul 07 23:46:59 merry systemd[46532]: systemd-suspend.service: Executing: /usr/lib/systemd/systemd-sleep suspend
Jul 07 23:46:59 merry systemd-sleep[46532]: Successfully forked off '(sd-executor)' as PID 46533.
Jul 07 23:46:59 merry [46533]: Successfully forked off '(direxec)' as PID 46534.
Jul 07 23:46:59 merry [46533]: /usr/lib/systemd/system-sleep/displaylink.sh succeeded.
Jul 07 23:46:59 merry systemd-sleep[46532]: (sd-executor) succeeded.
Jul 07 23:46:59 merry systemd-sleep[46532]: Bus n/a: changing state UNSET → OPENING
Jul 07 23:46:59 merry systemd-sleep[46532]: sd-bus: starting bus by connecting to /run/dbus/system_bus_socket...
Jul 07 23:46:59 merry systemd-sleep[46532]: Bus n/a: changing state OPENING → AUTHENTICATING
Jul 07 23:46:59 merry systemd-sleep[46532]: Bus n/a: changing state AUTHENTICATING → HELLO
Jul 07 23:46:59 merry systemd-sleep[46532]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Jul 07 23:46:59 merry systemd-sleep[46532]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.1078 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a
Jul 07 23:46:59 merry systemd-sleep[46532]: Bus n/a: changing state HELLO → RUNNING
Jul 07 23:46:59 merry systemd-sleep[46532]: Sent message type=method_call sender=n/a destination=org.freedesktop.home1 path=/org/freedesktop/home1 interface=org.freedesktop.home1.Manager member=LockAllHomes cookie=2 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Jul 07 23:46:59 merry systemd-sleep[46532]: Got message type=error sender=org.freedesktop.DBus destination=:1.1078 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=s error-name=org.freedesktop.DBus.Error.NameHasNoOwner error-message=Name "org.freedesktop.home1" does not exist
Jul 07 23:46:59 merry systemd-sleep[46532]: systemd-homed is not running, locking of home directories skipped.
Jul 07 23:46:59 merry systemd-sleep[46532]: Bus n/a: changing state RUNNING → CLOSED
Jul 07 23:46:59 merry systemd-sleep[46532]: Entering sleep state 'suspend'...
Jul 07 23:47:01 merry systemd-sleep[46532]: Failed to write 'mem' to /sys/power/state: No such file or directory
Jul 07 23:47:01 merry systemd-sleep[46532]: Failed to write 'standby' to /sys/power/state: Invalid argument
Jul 07 23:47:04 merry systemd-sleep[46532]: Failed to write 'freeze' to /sys/power/state: No such file or directory
Jul 07 23:47:04 merry systemd-sleep[46532]: Failed to put system to sleep. System resumed again: No such file or directory
Jul 07 23:47:04 merry systemd-sleep[46532]: Successfully forked off '(sd-executor)' as PID 46608.
Jul 07 23:47:04 merry [46608]: Successfully forked off '(direxec)' as PID 46609.
Jul 07 23:47:04 merry [46608]: /usr/lib/systemd/system-sleep/displaylink.sh succeeded.
Jul 07 23:47:04 merry systemd-sleep[46532]: (sd-executor) succeeded.
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Child 46532 belongs to systemd-suspend.service.
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Service will not restart (restart setting)
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Changed start -> failed
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Job 15546 systemd-suspend.service/start finished, result=failed
Jul 07 23:47:04 merry systemd[1]: Failed to start System Suspend.
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Unit entered failed state.
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Consumed 183ms CPU time.
Jul 07 23:47:04 merry systemd[1]: systemd-suspend.service: Control group is empty.Offline
Would you mind booting freshly, then doing a couple of systemctl suspend's until it stops working, and finally grab a complete journal and share it?
Also consider testing the other suggestions in my previous post.
Offline
I swear I'm trying, but the bug disappears when I try to reproduce it ![]()
As soon as I'm able to reproduce it consistently, I'll post the logs.
FTR, bluetooth is always disabled and I have nothing plugged in. I tried LTS, but haven't been able to reproduce the problem with it.
Offline