Arch Linux

theRedCyclops

Member

Registered: 2022-06-17

Posts: 60

[WORKAROUND] Failure to recover from suspend

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

oct 15 21:54:02 kheprix systemd-networkd[720]: wlp11s0: Link UP
oct 15 21:54:02 kheprix NetworkManager[886]: <info>  [1729022042.1818] device (p2p-dev-wlp11s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
oct 15 21:54:02 kheprix NetworkManager[886]: <info>  [1729022042.1818] manager: NetworkManager state is now ASLEEP
oct 15 21:54:02 kheprix systemd[1]: Reached target Sleep.
oct 15 21:54:02 kheprix systemd[1]: Starting System Suspend...
oct 15 21:54:02 kheprix wpa_supplicant[941]: wlp11s0: CTRL-EVENT-DSCP-POLICY clear_all
oct 15 21:54:02 kheprix systemd-sleep[1141]: Successfully froze unit 'user.slice'.
oct 15 21:54:02 kheprix systemd-sleep[1141]: Performing sleep operation 'suspend'...
oct 15 21:54:02 kheprix kernel: PM: suspend entry (deep)
oct 15 21:54:02 kheprix kernel: Filesystems sync: 0.010 seconds

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/XIHg.txt
I have now also tried to
Using AMD GPU
Not dual booting
luks & btrfs on ssd

nomodeset does not fix it
$SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0 does not fix it

Last edited by theRedCyclops (2024-11-01 15:20:45)

theRedCyclops

Member

Registered: 2022-06-17

Posts: 60

Re: [WORKAROUND] Failure to recover from suspend

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)

theRedCyclops

Member

Registered: 2022-06-17

Posts: 60

Re: [WORKAROUND] Failure to recover from suspend

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)

theRedCyclops

Member

Registered: 2022-06-17

Posts: 60

Re: [WORKAROUND] Failure to recover from suspend

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

btb45

Member

Registered: 2024-10-27

Posts: 5

Re: [WORKAROUND] Failure to recover from suspend

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.

theRedCyclops

Member

Registered: 2022-06-17

Posts: 60

Re: [WORKAROUND] Failure to recover from suspend

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