You are not logged in.
Recently I was forced to fully reinstall my system, everything seemed to be working, but I have noticed that whenever the computer is suspended it fails to resume
nov 25 20:08:49 kheprix systemd-logind[2014]: The system will suspend now!
nov 25 20:08:49 kheprix NetworkManager[2011]: <info> [1732561729.4710] manager: sleep: sleep requested (sleeping: no enabled: yes)
nov 25 20:08:49 kheprix NetworkManager[2011]: <info> [1732561729.4711] device (wlp11s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
nov 25 20:08:49 kheprix systemd-networkd[1309]: wlp11s0: Link DOWN
nov 25 20:08:49 kheprix NetworkManager[2011]: <info> [1732561729.5269] device (wlp11s0): set-hw-addr: reset MAC address to 34:6F:24:DA:79:AD (unmanage)
nov 25 20:08:49 kheprix systemd-networkd[1309]: wlp11s0: Link UP
nov 25 20:08:49 kheprix NetworkManager[2011]: <info> [1732561729.5542] device (p2p-dev-wlp11s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
nov 25 20:08:49 kheprix NetworkManager[2011]: <info> [1732561729.5542] manager: NetworkManager state is now ASLEEP
nov 25 20:08:49 kheprix systemd[1]: Reached target Sleep.
nov 25 20:08:49 kheprix systemd[1]: Starting System Suspend...
nov 25 20:08:49 kheprix wpa_supplicant[2079]: wlp11s0: CTRL-EVENT-DSCP-POLICY clear_all
nov 25 20:08:49 kheprix systemd-sleep[17542]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
nov 25 20:08:49 kheprix systemd-sleep[17542]: This is not recommended, and might result in unexpected behavior, particularly
nov 25 20:08:49 kheprix systemd-sleep[17542]: in suspend-then-hibernate operations or setups with encrypted home directories.
nov 25 20:08:49 kheprix systemd-sleep[17542]: Performing sleep operation 'suspend'...
is the last thing the system outputs to logs, after that when resuming the system the only thing that appears is a blinking cursor in case of a tty or the monitors fail to turn on if running a graphical session, I seemingly have no input from the keyboard
full logs: https://0x0.st/X5DY.txt
I have now also tried to
Using AMD GPU
Not dual booting
luks & btrfs on ssd (subvolumes for root, home, swap and snapshots)
using deep sleep mode
nomodeset does not fix it
$SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0 does not fix it
Linux LTS kernel works
edit: updated logs & added information
Last edited by theRedCyclops (2024-11-25 23:02:09)
Offline
I have tested reisub, but only the last (reboot) instruction actually works, the rest don't seem to respond, after checking a backup of the previous system for suspend related tasks I have now added
/etc/systemd/system/systemd-suspend.service.d/override.conf
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
because it seemed to fix the issue previously if I remember correctly, this time it didn't work
Last edited by theRedCyclops (2024-11-07 08:54:10)
Offline
It seems I had accidentally messed up the path, when I changed it to /etc/systemd/system/systemd-suspend.service.d/override.conf it finally fixed it, marking as solved It worked once, after further testing it doesn't work
Last edited by theRedCyclops (2024-10-20 19:17:11)
Offline
I finally managed to find a workaround, switching to the linux-lts kernel fixes the issue, I would still prefer to get the regular kernel working, if anyone knows a possible fix do comment
Offline
My notebook has been experiencing this issue for a few months, and have been using kernel lts as a workaround.
I investigated a bit and found this better workaround and can use regular kernels. I created the service...
/etc/systemd/system/systemd-suspend.service
[Unit]
Description=System Suspend
Documentation=man:systemd-suspend.service(8)
DefaultDependencies=no
Requires=sleep.target
After=sleep.target
[Service]
Type=oneshot
ExecStart=/usr/lib/systemd/systemd-sleep suspend
Environment=SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0
systemctl daemon-reload
...and now no hanging after resume from suspend.
I'm still very much learning, and not sure if all the parameters above are required but it works on my system so left it as is.
Offline
Thanks for the help, however I'm afraid that what you're proposing is equivalent to what I did in my second post, and as I've explained in the third, it worked once and stopped working after that
Offline
Just to be clear, if anyone knows another potential fix please notify me because I would much rather not get stuck with the LTS kernel
Offline