[SOLVED]Hibernate not working, code -16

fennewald · 2023-03-11 06:39:44

Hello!

I recently installed arch on my T14, and I'm having issues getting Hibernation to work.

My Problem

When I perform a hibernation with

systemctl hibernate

, my screen goes black like expected. When I attempt to wake my system from its slumber, though, it will think for ~10 seconds, flash my last opened screen for a moment, and then reboot.

Evidence

There is only the minimal:

Mar 11 00:32:33 alph systemd-logind[535]: The system will hibernate now!
Mar 11 00:32:33 alph ModemManager[551]: <info>  [sleep-monitor-systemd] system is about to suspend
Mar 11 00:32:33 alph sudo[2055]: pam_unix(sudo:session): session closed for user root
Mar 11 00:32:33 alph systemd[1]: Reached target Sleep.
Mar 11 00:32:33 alph systemd[1]: Starting Hibernate...
Mar 11 00:32:33 alph kernel: PM: Image not found (code -16)
Mar 11 00:32:33 alph systemd-sleep[2059]: Entering sleep state 'hibernate'...
Mar 11 00:32:33 alph kernel: PM: hibernation: hibernation entry
-- Boot 9dd236346ba84b8c9f4925c253f34da6 --

Errno 16 is EBUSY, which totally stumps me.

Here's a pastebin of a boot that consists of logging on on the tty, and then executing:

echo "User control here" | systemd-cat
systemctl hibernate

System Information

I have a 2TiB disk, laid out as such:

|      Disk      | Format | Mount Point |   Size  |               PARTUUID               |
|----------------|--------|-------------|---------|--------------------------------------|
| /dev/nvme0n1p1 |  vfat  |    /boot    |   1 GiB | 031c8093-0197-ab46-9765-73044b1bc349 |
| /dev/nvme0n1p2 |  swap  |  it's swap  |  80 GiB | 81bded5a-3918-534d-b605-dbb8c991d393 |
| /dev/nvme0n1p3 |  ext4  |      /      | 1.7 TiB | fabf062f-25d3-f74a-8522-4ce2db5f3621 |

I'm using systemd-boot, and my kernel command line parameters are:

initrd=\amd-ucode.img initrd=\initramfs-linux.img root="PARTUUID=fabf062f-25d3-f74a-8522-4ce2db5f3621" rw resume="PARTUUID=81bded5a-3918-534d-b605-dbb8c991d393" rw quiet

My swap partition loads correctly during boot. In fact, it will load even if I remove the associated fstab entry, which I take to mean it's being loaded by UEFI before I've even mounted and read my fstab. I do, however, leave the fstab entry in place.

Additionally, I have 48GiB of ram, and <4GiB ram usage with 0 swap usage when I attempt a hibernation, so there's definitely no concerns about not enough swap space.

What I've looked in to

The only relevant post I can find is this arch linux forum post, which had the same -16 error code. However, I am neither using a swapfile (I'm using a pure swap partition), and have the appropriate boot parameters in place. I'm out of ideas tbh, hence my first ever forum post!

Miscellaneous commands

Here's the output from a few commands that may be of interest:

[carson@alph ~]$ lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0  1.8T  0 disk
├─nvme0n1p1 259:1    0    1G  0 part /boot
├─nvme0n1p2 259:2    0   80G  0 part [SWAP]
└─nvme0n1p3 259:3    0  1.7T  0 part /
[carson@alph ~]$ blkid
/dev/nvme0n1p3: UUID="54df3c64-ce1d-402a-89b3-e911664af775" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="fabf062f-25d3-f74a-8522-4ce2db5f3621"
/dev/nvme0n1p1: UUID="9815-17C5" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="031c8093-0197-ab46-9765-73044b1bc349"
/dev/nvme0n1p2: UUID="f9ce891f-825a-466f-b5ee-18c599778d1f" TYPE="swsuspend" PARTUUID="81bded5a-3918-534d-b605-dbb8c991d393"
[carson@alph ~]$ swapon --show
NAME           TYPE      SIZE USED PRIO
/dev/nvme0n1p2 partition  80G   0B   -2
[carson@alph ~]$ bootctl | cat
System:
      Firmware: UEFI 2.70 (Lenovo 0.4240)
 Firmware Arch: x64
   Secure Boot: disabled (disabled)
  TPM2 Support: yes
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 253-1-arch
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
               ✓ Support for XBOOTLDR partition
               ✓ Support for passing random seed to OS
               ✓ Load drop-in drivers
               ✓ Support Type #1 sort-key field
               ✓ Support @saved pseudo-entry
               ✓ Support Type #1 devicetree field
               ✓ Boot loader sets ESP information
          ESP: /dev/disk/by-partuuid/031c8093-0197-ab46-9765-73044b1bc349
         File: └─/EFI/systemd/systemd-bootx64.efi

Random Seed:
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/031c8093-0197-ab46-9765-73044b1bc349)
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 253-1-arch)
               └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 253-1-arch)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/031c8093-0197-ab46-9765-73044b1bc349
         File: └─/EFI/systemd/systemd-bootx64.efi

        Title: Arch
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/031c8093-0197-ab46-9765-73044b1bc349
         File: └─/vmlinuz-linux

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/031c8093-0197-ab46-9765-73044b1bc349)
        token: arch

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: Arch Linux
           id: arch.conf
       source: /boot//loader/entries/arch.conf
        linux: /boot//vmlinuz-linux
       initrd: /boot//amd-ucode.img
               /boot//initramfs-linux.img
      options: root="PARTUUID=fabf062f-25d3-f74a-8522-4ce2db5f3621" rw resume="PARTUUID=81bded5a-3918-534d-b605-dbb8c991d393" rw quiet

Last edited by fennewald (2023-03-11 14:39:26)

seth · 2023-03-11 08:48:49

Did you try to address the swap partition by its UUID instead of PARTUUID?

fennewald · 2023-03-11 11:37:47

Did you try to address the swap partition by its UUID instead of PARTUUID?

Just tried this. No change

seth · 2023-03-11 13:10:23

nvme shenanigans?
Does it work w/ "nvme_core.default_ps_max_latency_us=0 iommu=soft" ?

fennewald · 2023-03-11 13:51:09

No change with the updated parameters

seth · 2023-03-11 14:00:50

Meh.
Tried to swapoff the partition?

fennewald · 2023-03-11 14:38:36

I've fixed it. This is embarrassing, but re-reading the arch wiki page I realized I never added an appropriate mkinitcpio hook. I added resume to my hooks, rebooted, and everything is working now. Thank you for bearing with me!

mustafa_nasser · 2023-03-11 22:21:29

I'm facing same problem but after I added the resume hook ......... Does it Work consistently 100% of the time ?

fennewald · 2023-03-12 06:08:48

mustafa_nasser wrote:

I'm facing same problem but after I added the resume hook ......... Does it Work consistently 100% of the time ?

I'm currently 4/4 hibernations, but I will post here if I run into a failure.

seth · 2023-03-12 07:00:08

@mustafa_nasser, there's a good chance that you misconfigured the system in a totally different way
Open a new thread and post your system journal as well as

lsblk -o NAME,FSTYPE,UUID,PARTUUID,LABEL

mustafa_nasser · 2023-03-12 09:53:14

I posted already ? I will add this command output to it

alexindigo · 2026-01-10 03:25:18

I'm seeing similar issue, it's just my system freezes after monitor goes dark and auto-opens back up, but journal logs are the same (this is how I found this issue).
As for mkinitcpio hooks, this is what I see in the wiki:

> Configure the initramfs
> When an initramfs with the systemd hook is used, which is the default, a resume mechanism is already provided, and no further hooks need to be added.

Sounds like I don't need to manually add `resume` hook, since I already have `systemd` hook
Did I miss anything?

Update: Adding hook and kernel param didn't help, I see `(code -16)` is gone from logs, but symptoms haven't changed.

```
Jan 09 20:16:25 ark systemd-logind[1582]: The system will hibernate now!
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.1395] manager: sleep: sleep requested (sleeping: no ena>
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.1397] device (eno1np0): state change: unavailable -> unm>
Jan 09 20:16:25 ark sudo[1787]: pam_unix(sudo:session): session closed for user root
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.1600] device (eno2np1): state change: unavailable -> unm>
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.1782] device (wlo5): state change: disconnected -> unman>
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2004] device (wlo5): set-hw-addr: reset MAC address to E>
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2035] device (p2p-dev-wlo5): state change: disconnected >
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2035] manager: NetworkManager state is now DISABLED (ASL>
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2037] device (eno3): state change: activated -> deactiva>
Jan 09 20:16:25 ark systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 09 20:16:25 ark wpa_supplicant[1619]: p2p-dev-wlo5: CTRL-EVENT-DSCP-POLICY clear_all
Jan 09 20:16:25 ark wpa_supplicant[1619]: p2p-dev-wlo5: CTRL-EVENT-DSCP-POLICY clear_all
Jan 09 20:16:25 ark wpa_supplicant[1619]: nl80211: deinit ifname=p2p-dev-wlo5 disabled_11b_rates=0
Jan 09 20:16:25 ark systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 09 20:16:25 ark wpa_supplicant[1619]: wlo5: CTRL-EVENT-DSCP-POLICY clear_all
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2434] device (eno3): state change: deactivating -> disco>
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2437] dhcp4 (eno3): canceled DHCP transaction
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2438] dhcp4 (eno3): activation: beginning transaction (t>
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2438] dhcp4 (eno3): state changed no lease
Jan 09 20:16:25 ark wpa_supplicant[1619]: wlo5: CTRL-EVENT-DSCP-POLICY clear_all
Jan 09 20:16:25 ark wpa_supplicant[1619]: nl80211: deinit ifname=wlo5 disabled_11b_rates=0
Jan 09 20:16:25 ark NetworkManager[1580]: <info> [1768018585.2677] device (eno3): state change: disconnected -> unman>
Jan 09 20:16:25 ark kernel: r8169 0000:ab:00.0 eno3: Link is Down
Jan 09 20:16:25 ark systemd[1]: Reached target Sleep.
Jan 09 20:16:25 ark systemd[1]: Starting System Hibernate...
Jan 09 20:16:25 ark systemd[1]: user.slice: Unit now frozen.
Jan 09 20:16:25 ark systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Jan 09 20:16:25 ark systemd[1]: session-1.scope: Unit now frozen-by-parent.
Jan 09 20:16:25 ark systemd-sleep[1804]: Successfully froze unit 'user.slice'.
Jan 09 20:16:25 ark systemd[1]: user@1000.service: Unit now frozen-by-parent.
Jan 09 20:16:25 ark systemd-sleep[1804]: Performing sleep operation 'hibernate'...
Jan 09 20:16:25 ark kernel: PM: hibernation: hibernation entry
```

Last edited by alexindigo (2026-01-10 04:25:00)

seth · 2026-01-10 10:04:06

1. Please use [code][/code] tags, the BBS predates markdown.
2. Don't copy and paste out of the pager as it truncates lines
3. Please don't necrobump - chances are, you're not facing the situation that has existed 3 years ago
4. Please open a new thread, explain the symptoms and post your complete system journal for the boot before and after the wakeup

(sudo journalctl -b -1; sudo journalctl -b) | curl -F 'file=@-' 0x0.st

There's currently a bug between gnome and systemd where gnome will always sleep twice in a row, https://bbs.archlinux.org/viewtopic.php?id=308457 - which might be at play if you're using gnome

V1del · 2026-01-10 12:11:06

As mentioned above please open a new thread addressing the points mentioned.

Closing this old thread.

Arch Linux

#1 2023-03-11 06:39:44