Problems with getting hibernation to work

sebbas · 2023-09-25 22:18:09

Hi, first post, so I'm putting it in newbie corner just to be safe

So, I'm trying to get hibernation (suspend to disk) to work on my system.
The current problem is that if I tell the system to hibernate (either through the GUI or with systemctl hibernate), the system will lock the screen, and then resume.
It doesn't look like it gets to the step of turning the system of. After that the system works fine, apart from not suspending of course.

Arch is installed with an LVM on LUKS setup as described here: https://wiki.archlinux.org/title/Dm-cry … VM_on_LUKS
The system has three logical volumes (root, home, swap), the swap partition is 20G.
That 20G should be enough for the 8G of ram.
I have set the following kernel arguments in /etc/default/grub:

GRUB_CMDLINE_LINUX="cryptdevice=UUID=6adf1488-763d-41bf-868a-750b72dd0981:cryptlvm root=/dev/sys/root resume=/dev/sys/swap"

I have set the following hooks /etc/mkinitcpio.conf:

HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block encrypt lvm2 filesystems resume fsck)

referencing:
https://wiki.archlinux.org/title/Dm-cry … initcpio_2
and
https://wiki.archlinux.org/title/Power_ … _initramfs

I checked the output of journalctl after the failed hibernation and these seem to be the relevant logs:

systemd[1]: Reached target Sleep.
systemd[1]: Starting Hibernate...
wpa_supplicant[745]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
systemd-sleep[142955]: Entering sleep state 'hibernate'...
kernel: PM: hibernation: hibernation entry
kscreenlocker_greet[142906]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
wpa_supplicant[745]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[745]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
kernel: Filesystems sync: 0.033 seconds
kernel: Freezing user space processes
kernel: Freezing user space processes completed (elapsed 0.023 seconds)
kernel: OOM killer disabled.
kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
kernel: PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff]
kernel: PM: hibernation: Marking nosave pages: [mem 0x09c00000-0x09da0fff]
kernel: PM: hibernation: Marking nosave pages: [mem 0x09f00000-0x09f0bfff]
kernel: PM: hibernation: Marking nosave pages: [mem 0x98f0a000-0x98f0afff]
kernel: PM: hibernation: Marking nosave pages: [mem 0x98f17000-0x98f17fff]
kernel: PM: hibernation: Marking nosave pages: [mem 0xc030f000-0xc039ffff]
kernel: PM: hibernation: Marking nosave pages: [mem 0xc3239000-0xc3239fff]
kernel: PM: hibernation: Marking nosave pages: [mem 0xc4b7e000-0xcc1fdfff]
kernel: PM: hibernation: Marking nosave pages: [mem 0xce000000-0xffffffff]
kernel: PM: hibernation: Basic memory bitmaps created
kernel: PM: hibernation: Preallocating image memory
kernel: PM: hibernation: Image allocation is 112311 pages short
kernel: PM: hibernation: Basic memory bitmaps freed
kernel: OOM killer enabled.
kernel: Restarting tasks ... done.
kernel: PM: hibernation: hibernation exit
systemd-sleep[142955]: Failed to put system to sleep. System resumed again: Cannot allocate memory
rtkit-daemon[951]: The canary thread is apparently starving. Taking action.
rtkit-daemon[951]: Demoting known real-time threads.
rtkit-daemon[951]: Demoted 0 threads.
systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Hibernate.
systemd[1]: Dependency failed for System Hibernation.
systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.
systemd[1]: systemd-hibernate.service: Consumed 4.498s CPU time.
systemd[1]: Stopped target Sleep.
systemd-logind[715]: Operation 'sleep' finished.

What stands out is:

systemd-sleep[142955]: Failed to put system to sleep. System resumed again: Cannot allocate memory

I also ended up checking the /dev/power/image_size value since it was mentioned in another forum post, which is set to 2812174336.
That might be to small, but https://docs.kernel.org/admin-guide/pm/ … ibernation says that the kernel will make the hibernation image larger if needed, so I don't know if it matters.

All that said, I dont know where to proceed from here. Do i just have to little ram to suspend to disk (I mean I do have 8G plus 20G of swap, and at least most of the swap remains unused)?
Or is there some other parameter I can mess with?

seth · 2023-09-26 06:29:51

https://wiki.archlinux.org/title/Dm-cry … tcpio_hook - blue note.
Have you tried to hibernate into a swapfile?

Arch Linux

#1 2023-09-25 22:18:09

Problems with getting hibernation to work

#2 2023-09-26 06:29:51

Re: Problems with getting hibernation to work

Board footer