Hi,
I’m having an issue where my system fails to wake up correctly after suspending. I cannot open another terminal and I am forced to hard shutdown the system with the power button. This just started after an update, though my system was maybe a month out of date prior to this.
Upon resuming, the screen displays a log of the suspend process. I thought the displayed error messages were at fault at first, but I think they’re a normal part of the suspend process. What isn’t normal is that it looks like the kernel suspends before suspending user processes, and then continues the suspend process when it should be resuming. Here’s a relevant portion of the logs:
Aug 09 21:47:30 [] systemd[1]: Reached target Sleep.
Aug 09 21:47:30 [] systemd[1]: Starting System Suspend...
Aug 09 21:47:30 [] systemd-sleep[6940]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Aug 09 21:47:30 [] systemd-sleep[6940]: This is not recommended, and might result in unexpected behavior, particularly
Aug 09 21:47:30 [] systemd-sleep[6940]: in suspend-then-hibernate operations or setups with encrypted home directories.
Aug 09 21:47:30 [] systemd-sleep[6940]: Performing sleep operation 'suspend'...
Aug 09 21:47:30 [] kernel: PM: suspend entry (deep)
Aug 09 21:47:30 [] kernel: Filesystems sync: 0.001 seconds
Aug 10 16:49:14 [] kernel: Freezing user space processes
Aug 10 16:49:14 [] kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Aug 10 16:49:14 [] kernel: OOM killer disabled.
Note the timestamps. The suspend process continues when I woke the machine the next day. Googling has shown me a few other instances of people encountering this, but it’s all from several years ago.(links below) I don’t know what would have changed in the past month or so that would have reintroduced this issue.