I am sorry, my mistake. This
was second attempt of trying some advice I found on arch forums. I of course tried it after this
didn’t change the cmdline too.
But let’s not talk the swap stuff please. Does anything come to your mind with the main problematics of this thread?
without this it will not update the grub.cfg used on boot up with grub.
if hibernate does not powerdown this looks basically like something in Bios set to not allow fully power down some Firmware has options for used power states.
And to check what exactly is happening you could check powerdown journal:
journalctl -b -1 -e
or
journalctl -b -1 | grep -i shutdown
And test if it is the same for other kernels like linux-lts or linux-zen
But if resume target is not properly set.. hibernate will not work properly
I have posted the output of the
in one of the above posts:
In order to try at least something, I have installed the linux-zen, but it resulted into same problem. The output of journal since the beginning of the hibernation using linux-zen is the following
kvě 05 18:30:06 m-82jq systemd-logind[1656]: The system will hibernate now!
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.8304] manager: sleep: sleep requested (sleeping: no enabled: yes)
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.8305] device (eno1): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping>
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.8371] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'unmanage>
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.8372] manager: NetworkManager state is now ASLEEP
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.8374] device (wlan0): state change: activated -> deactivating (reason 'sleeping', manag>
kvě 05 18:30:06 m-82jq systemd[1]: Starting Network Manager Script Dispatcher Service...
kvě 05 18:30:06 m-82jq systemd[1]: Started Network Manager Script Dispatcher Service.
kvě 05 18:30:06 m-82jq kernel: wlan0: deauthenticating from 98:25:4a:9c:08:94 by local choice (Reason: 3=DEAUTH_LEAVING)
kvě 05 18:30:06 m-82jq wpa_supplicant[1816]: nl80211: send_event_marker failed: Source based routing not supported
kvě 05 18:30:06 m-82jq wpa_supplicant[1816]: wlan0: CTRL-EVENT-DISCONNECTED bssid=98:25:4a:9c:08:94 reason=3 locally_generated=1
kvě 05 18:30:06 m-82jq wpa_supplicant[1816]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.9393] device (wlan0): supplicant interface state: completed -> disconnected
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.9395] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', ma>
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Withdrawing address record for fe80::f99f:c65f:13e:292c on wlan0.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::f99f:c65f:13e:292c.
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.9397] dhcp4 (wlan0): canceled DHCP transaction
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Interface wlan0.IPv6 no longer relevant for mDNS.
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.9397] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.9397] dhcp4 (wlan0): state changed no lease
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Interface wlan0.IPv4 no longer relevant for mDNS.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.238.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Withdrawing address record for 192.168.0.238 on wlan0.
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.9635] device (wlan0): set-hw-addr: set MAC address to 6E:8E:8D:A4:D1:40 (scanning)
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.238.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: New relevant interface wlan0.IPv4 for mDNS.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Registering new address record for 192.168.0.238 on wlan0.IPv4.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Withdrawing address record for 192.168.0.238 on wlan0.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.238.
kvě 05 18:30:06 m-82jq avahi-daemon[1631]: Interface wlan0.IPv4 no longer relevant for mDNS.
kvě 05 18:30:06 m-82jq NetworkManager[1749]: <info> [1746462606.9855] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-sleepi>
kvě 05 18:30:07 m-82jq NetworkManager[1749]: <info> [1746462607.1132] device (wlan0): set-hw-addr: reset MAC address to 64:BC:58:A2:6E:3A (unmanage)
kvě 05 18:30:07 m-82jq wpa_supplicant[1816]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
kvě 05 18:30:07 m-82jq wpa_supplicant[1816]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
kvě 05 18:30:07 m-82jq wpa_supplicant[1816]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
kvě 05 18:30:07 m-82jq systemd[1]: Reached target Sleep.
kvě 05 18:30:07 m-82jq systemd[1]: Starting NVIDIA system hibernate actions...
kvě 05 18:30:07 m-82jq hibernate[4236]: nvidia-hibernate.service
kvě 05 18:30:07 m-82jq logger[4236]: <13>May 5 18:30:07 hibernate: nvidia-hibernate.service
kvě 05 18:30:07 m-82jq wpa_supplicant[1816]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
kvě 05 18:30:07 m-82jq wpa_supplicant[1816]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
kvě 05 18:30:07 m-82jq wpa_supplicant[1816]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
kvě 05 18:30:08 m-82jq systemd[1]: nvidia-hibernate.service: Deactivated successfully.
kvě 05 18:30:08 m-82jq systemd[1]: Finished NVIDIA system hibernate actions.
kvě 05 18:30:08 m-82jq systemd[1]: Starting System Hibernate...
kvě 05 18:30:08 m-82jq systemd-sleep[4269]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
kvě 05 18:30:08 m-82jq systemd-sleep[4269]: This is not recommended, and might result in unexpected behavior, particularly
kvě 05 18:30:08 m-82jq systemd-sleep[4269]: in suspend-then-hibernate operations or setups with encrypted home directories.
kvě 05 18:30:08 m-82jq systemd-sleep[4269]: Performing sleep operation 'hibernate'...
kvě 05 18:30:08 m-82jq kernel: PM: hibernation: hibernation entry
I am not so experienced to find anything helpful there. I can see there is some problem with send_event_marker, but I don’t expect it to corelate with the laptop not shutting down.
I haven’t touched bios for years, and i double checked ti is on it’s latest version (2023 update).
If there is problem with the swap, it should be mentioned in the journal, shouldn’t it?
This is output of journalctl on my second laptop with basically identical system installed:
May 05 21:11:33 m-82jq systemd-logind[1215]: The system will hibernate now!
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.4498] manager: sleep: sleep requested (sleeping: no enabled: yes)
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.4499] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.4502] manager: NetworkManager state is now ASLEEP
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.4503] device (wlan0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
May 05 21:11:33 m-82jq systemd[1]: Starting Network Manager Script Dispatcher Service...
May 05 21:11:33 m-82jq systemd[1]: Started Network Manager Script Dispatcher Service.
May 05 21:11:33 m-82jq kernel: wlan0: deauthenticating from 98:25:4a:9c:08:94 by local choice (Reason: 3=DEAUTH_LEAVING)
May 05 21:11:33 m-82jq wpa_supplicant[1304]: nl80211: send_event_marker failed: Source based routing not supported
May 05 21:11:33 m-82jq wpa_supplicant[1304]: wlan0: CTRL-EVENT-DISCONNECTED bssid=98:25:4a:9c:08:94 reason=3 locally_generated=1
May 05 21:11:33 m-82jq wpa_supplicant[1304]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.7268] device (wlan0): supplicant interface state: completed -> disconnected
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.7271] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
May 05 21:11:33 m-82jq avahi-daemon[1210]: Withdrawing address record for fe80::8907:e0ce:fcf7:3d8a on wlan0.
May 05 21:11:33 m-82jq avahi-daemon[1210]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::8907:e0ce:fcf7:3d8a.
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.7275] dhcp4 (wlan0): canceled DHCP transaction
May 05 21:11:33 m-82jq avahi-daemon[1210]: Interface wlan0.IPv6 no longer relevant for mDNS.
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.7275] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.7275] dhcp4 (wlan0): state changed no lease
May 05 21:11:33 m-82jq avahi-daemon[1210]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 05 21:11:33 m-82jq avahi-daemon[1210]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.135.
May 05 21:11:33 m-82jq avahi-daemon[1210]: Withdrawing address record for 192.168.0.135 on wlan0.
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.7470] device (wlan0): set-hw-addr: set MAC address to AA:B0:80:55:8F:61 (scanning)
May 05 21:11:33 m-82jq avahi-daemon[1210]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.135.
May 05 21:11:33 m-82jq avahi-daemon[1210]: New relevant interface wlan0.IPv4 for mDNS.
May 05 21:11:33 m-82jq avahi-daemon[1210]: Registering new address record for 192.168.0.135 on wlan0.IPv4.
May 05 21:11:33 m-82jq avahi-daemon[1210]: Withdrawing address record for 192.168.0.135 on wlan0.
May 05 21:11:33 m-82jq avahi-daemon[1210]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.135.
May 05 21:11:33 m-82jq avahi-daemon[1210]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 05 21:11:33 m-82jq NetworkManager[1242]: <info> [1746472293.9960] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
May 05 21:11:34 m-82jq NetworkManager[1242]: <info> [1746472294.0200] device (wlan0): set-hw-addr: reset MAC address to 54:6C:EB:5A:CC:33 (unmanage)
May 05 21:11:34 m-82jq systemd[1]: Reached target Sleep.
May 05 21:11:34 m-82jq systemd[1]: Starting NVIDIA system hibernate actions...
May 05 21:11:34 m-82jq wpa_supplicant[1304]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
May 05 21:11:34 m-82jq wpa_supplicant[1304]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
May 05 21:11:34 m-82jq wpa_supplicant[1304]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
May 05 21:11:34 m-82jq hibernate[5063]: nvidia-hibernate.service
May 05 21:11:34 m-82jq logger[5063]: <13>May 5 21:11:34 hibernate: nvidia-hibernate.service
May 05 21:11:34 m-82jq systemd[1]: nvidia-hibernate.service: Deactivated successfully.
May 05 21:11:34 m-82jq systemd[1]: Finished NVIDIA system hibernate actions.
May 05 21:11:34 m-82jq systemd[1]: Starting System Hibernate...
May 05 21:11:34 m-82jq systemd-sleep[5067]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
May 05 21:11:34 m-82jq systemd-sleep[5067]: This is not recommended, and might result in unexpected behavior, particularly
May 05 21:11:34 m-82jq systemd-sleep[5067]: in suspend-then-hibernate operations or setups with encrypted home directories.
May 05 21:11:34 m-82jq wpa_supplicant[1304]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
May 05 21:11:34 m-82jq wpa_supplicant[1304]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
May 05 21:11:34 m-82jq wpa_supplicant[1304]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
May 05 21:11:34 m-82jq systemd-sleep[5067]: Performing sleep operation 'hibernate'...
May 05 21:11:34 m-82jq kernel: PM: hibernation: hibernation entry
May 05 21:11:35 m-82jq kernel: Filesystems sync: 1.486 seconds
May 05 21:12:33 m-82jq kernel: Freezing user space processes
May 05 21:12:33 m-82jq kernel: Freezing user space processes completed (elapsed 0.001 seconds)
May 05 21:12:33 m-82jq kernel: OOM killer disabled.
May 05 21:12:33 m-82jq kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
May 05 21:12:33 m-82jq kernel: PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff]
May 05 21:12:33 m-82jq kernel: PM: hibernation: Marking nosave pages: [mem 0x3caad000-0x3cc07fff]
May 05 21:12:33 m-82jq kernel: PM: hibernation: Marking nosave pages: [mem 0x3d098000-0x3d098fff]
May 05 21:12:33 m-82jq kernel: PM: hibernation: Marking nosave pages: [mem 0x40d99000-0x41698fff]
May 05 21:12:33 m-82jq kernel: PM: hibernation: Marking nosave pages: [mem 0x434af000-0x45bfefff]
May 05 21:12:33 m-82jq kernel: PM: hibernation: Marking nosave pages: [mem 0x45c00000-0xffffffff]
May 05 21:12:33 m-82jq kernel: PM: hibernation: Basic memory bitmaps created
May 05 21:12:33 m-82jq kernel: PM: hibernation: Preallocating image memory
May 05 21:12:33 m-82jq kernel: PM: hibernation: Allocated 1106158 pages for snapshot
May 05 21:12:33 m-82jq kernel: PM: hibernation: Allocated 4424632 kbytes in 0.65 seconds (6807.12 MB/s)
May 05 21:12:33 m-82jq kernel: Freezing remaining freezable tasks
May 05 21:12:33 m-82jq kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
May 05 21:12:33 m-82jq kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 05 21:12:33 m-82jq kernel: ACPI: EC: interrupt blocked
May 05 21:12:33 m-82jq kernel: ACPI: PM: Preparing to enter system sleep state S4
May 05 21:12:33 m-82jq kernel: ACPI: EC: event blocked
May 05 21:12:33 m-82jq kernel: ACPI: EC: EC stopped
May 05 21:12:33 m-82jq kernel: ACPI: PM: Saving platform NVS memory
May 05 21:12:33 m-82jq kernel: Disabling non-boot CPUs ...
May 05 21:12:33 m-82jq kernel: smpboot: CPU 7 is now offline
May 05 21:12:33 m-82jq kernel: smpboot: CPU 6 is now offline
May 05 21:12:33 m-82jq kernel: smpboot: CPU 5 is now offline
May 05 21:12:33 m-82jq kernel: smpboot: CPU 4 is now offline
May 05 21:12:33 m-82jq kernel: smpboot: CPU 3 is now offline
May 05 21:12:33 m-82jq kernel: smpboot: CPU 2 is now offline
May 05 21:12:33 m-82jq kernel: smpboot: CPU 1 is now offline
May 05 21:12:33 m-82jq kernel: PM: hibernation: Creating image:
May 05 21:12:33 m-82jq kernel: PM: hibernation: Need to copy 1080585 pages
May 05 21:12:33 m-82jq kernel: PM: hibernation: Normal pages needed: 1080585 + 1024, available pages: 3056962
May 05 21:12:33 m-82jq kernel: ACPI: PM: Hardware changed while hibernated, success doubtful!
May 05 21:12:33 m-82jq kernel: ACPI: PM: Restoring platform NVS memory
May 05 21:12:34 m-82jq kernel: ACPI: EC: EC started
May 05 21:12:34 m-82jq kernel: Enabling non-boot CPUs ...
May 05 21:12:34 m-82jq kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
May 05 21:12:34 m-82jq kernel: resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000fedcdfff], which spans more than pnp 00:04 [mem 0xfedc0000-0xfedc7fff]
May 05 21:12:34 m-82jq kernel: caller uncore_get_box_mmio_addr+0xe7/0x150 [intel_uncore] mapping multiple BARs
May 05 21:12:34 m-82jq kernel: CPU1 is up
May 05 21:12:34 m-82jq kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
May 05 21:12:34 m-82jq kernel: CPU2 is up
May 05 21:12:34 m-82jq kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
May 05 21:12:34 m-82jq kernel: CPU3 is up
May 05 21:12:34 m-82jq kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
May 05 21:12:34 m-82jq kernel: CPU4 is up
May 05 21:12:34 m-82jq kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
May 05 21:12:34 m-82jq kernel: CPU5 is up
May 05 21:12:34 m-82jq kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
May 05 21:12:34 m-82jq kernel: CPU6 is up
May 05 21:12:34 m-82jq kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
May 05 21:12:34 m-82jq kernel: CPU7 is up
May 05 21:12:34 m-82jq kernel: ACPI: PM: Waking up from system sleep state S4
May 05 21:12:34 m-82jq kernel: ACPI: EC: interrupt unblocked
May 05 21:12:34 m-82jq kernel: ACPI: EC: event unblocked
May 05 21:12:34 m-82jq kernel: usb usb1: root hub lost power or was reset
May 05 21:12:34 m-82jq kernel: usb usb2: root hub lost power or was reset
May 05 21:12:34 m-82jq kernel: usb usb3: root hub lost power or was reset
May 05 21:12:34 m-82jq kernel: usb usb4: root hub lost power or was reset
May 05 21:12:34 m-82jq kernel: nvme nvme0: 8/0/0 default/read/poll queues
May 05 21:12:34 m-82jq kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
May 05 21:12:34 m-82jq kernel: usb 3-10: WARN: invalid context state for evaluate context command.
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: CSR_RESET = 0x10
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x0
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 0]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 1]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 2]: 0x3f1d0430
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 3]: 0x3f1d0430
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 4]: 0x3f1d0430
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 5]: 0x3f1d0430
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 6]: 0x3f1d0430
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 7]: 0x3f1d0430
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 8]: 0x3f1d0430
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 9]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 10]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 11]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 12]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 13]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 14]: 0x3f1d0030
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x1
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 0]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 1]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 2]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 3]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 4]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 5]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 6]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 7]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 8]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 9]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 10]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 11]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 12]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 13]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 14]: 0x040066c2
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x6
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 0]: 0xb00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 1]: 0xe00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 2]: 0xa00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 3]: 0xe00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 4]: 0xa00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 5]: 0xe00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 6]: 0xe00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 7]: 0xb00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 8]: 0xf00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 9]: 0xb00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 10]: 0xf00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 11]: 0xb00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 12]: 0xf00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 13]: 0xb00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 14]: 0xa00c7c75
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: Host monitor block 0x22 vector 0x0
May 05 21:12:34 m-82jq kernel: iwlwifi 0000:00:14.3: value [iter 0]: 0x41cec019
May 05 21:12:34 m-82jq kernel: usb 3-10: reset full-speed USB device number 3 using xhci_hcd
May 05 21:12:34 m-82jq kernel: ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1
May 05 21:12:34 m-82jq kernel: usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
May 05 21:12:34 m-82jq kernel: usb 3-1: reset high-speed USB device number 2 using xhci_hcd
May 05 21:12:34 m-82jq kernel: usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
May 05 21:12:34 m-82jq kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
May 05 21:12:34 m-82jq kernel: PM: hibernation: Basic memory bitmaps freed
May 05 21:12:34 m-82jq kernel: OOM killer enabled.
May 05 21:12:34 m-82jq kernel: Restarting tasks ...
May 05 21:12:34 m-82jq kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
May 05 21:12:34 m-82jq kernel: done.
May 05 21:12:34 m-82jq kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
May 05 21:12:34 m-82jq kernel: Bluetooth: hci0: Boot Address: 0x24800
May 05 21:12:34 m-82jq kernel: Bluetooth: hci0: Firmware Version: 132-3.24
May 05 21:12:34 m-82jq kernel: Bluetooth: hci0: Firmware already loaded
May 05 21:12:34 m-82jq kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 05 21:12:34 m-82jq kernel: efivarfs: resyncing variable state
May 05 21:12:34 m-82jq kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
May 05 21:12:34 m-82jq kernel: PM: hibernation: hibernation exit
May 05 21:12:33 m-82jq systemd[1]: Starting Load/Save RF Kill Switch Status...
May 05 21:12:33 m-82jq suspend[5393]: nvidia-resume.service
May 05 21:12:33 m-82jq systemd[1713]: Stopped target Bluetooth.
May 05 21:12:34 m-82jq logger[5393]: <13>May 5 21:12:33 suspend: nvidia-resume.service
May 05 21:12:33 m-82jq systemd[1]: Stopped target Bluetooth Support.
May 05 21:12:33 m-82jq systemd[1713]: Reached target Bluetooth.
May 05 21:12:33 m-82jq systemd[1]: Started Load/Save RF Kill Switch Status.
May 05 21:12:33 m-82jq systemd[1]: Reached target Bluetooth Support.
May 05 21:12:33 m-82jq systemd-sleep[5067]: System returned from sleep operation 'hibernate'.
May 05 21:12:33 m-82jq systemd[1]: systemd-hibernate.service: Deactivated successfully.
May 05 21:12:33 m-82jq systemd[1]: Finished System Hibernate.
May 05 21:12:33 m-82jq systemd[1]: systemd-hibernate.service: Consumed 1.292s CPU time, 9.5M memory peak.
May 05 21:12:33 m-82jq systemd[1]: Reached target System Hibernation.
May 05 21:12:33 m-82jq systemd[1]: Stopped target Sleep.
May 05 21:12:33 m-82jq systemd-logind[1215]: Operation 'hibernate' finished.
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4426] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4427] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4438] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
May 05 21:12:33 m-82jq systemd[1]: Starting NVIDIA system resume actions...
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4440] manager: NetworkManager state is now CONNECTED_LOCAL
May 05 21:12:33 m-82jq systemd[1]: Stopped target System Hibernation.
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4652] device (wlan0): supplicant interface state: internal-starting -> disconnected
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4653] device (p2p-dev-wlan0): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4657] Wi-Fi P2P device controlled by interface wlan0 created
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4659] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6)
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4661] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4668] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
May 05 21:12:33 m-82jq NetworkManager[1242]: <info> [1746472353.4676] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
May 05 21:12:33 m-82jq systemd[1]: nvidia-resume.service: Deactivated successfully.
May 05 21:12:33 m-82jq systemd[1]: Finished NVIDIA system resume actions.
Maybe let’s go back one step: Does your hibernate work when called from the shutdown menu? Mine (on Cinnamon) has both “suspend” and “hibernate”, and both function. Note hibernation requires a swap of RAM size + a little extra (because it writes RAM contents to the swap).
My hibernate works from shutdown menu the same way as systemctl hibernate, both resulting in succesful hibernation NOT followed by complete shutdown of the machine.
The suspend works as expected.
My ram is 13 Gi - free -h:
total used free shared buff/cache available
Mem: 13Gi 3,0Gi 8,5Gi 166Mi 2,5Gi 10Gi
Swap: 34Gi 0B 34Gi
As you can see, the Swap is more then sufficient. I have added a swapfile which is probably not set up properly to resume target, but the swap partition with SIZE of14.9G should do the trick by itself - swapon :
NAME TYPE SIZE USED PRIO
/swapfile file 20G 0B -2
/dev/sda3 partition 14,9G 0B -3
Thanks, you’re right—looks like it should function.
Another idea: I once had a machine where you could set desired “sleep states” (S3/S4/S5) in the BIOS, can you check that? Dreaded Windows “Quickstart” seems to use S4, while complete shutdown should be S5. (I think.)
I haven’t found anything like that in the settings. Maybe I should also mention that I dualboot with windows on which it’s hibernation works fine.
Hmm, that’s odd. No more ideas here, sorry. Maybe someone more knowledgeable has an idea for further diagnosis.
maybe wating next kernel 6.14.5
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.14.5
Author: Mario Limonciello mario.limonciello@amd.com
Date: Tue Apr 8 13:09:57 2025 -0500
drm/amd: Forbid suspending into non-default suspend states
[ Upstream commit 1657793def101dac7c9d3b2250391f6a3dd934ba ]
On systems that default to 'deep' some userspace software likes
to try to suspend in 'deep' first. If there is a failure for any
reason (such as -ENOMEM) the failure is ignored and then it will
try to use 's2idle' as a fallback. This fails, but more importantly
it leads to graphical problems.
Forbid this behavior and only allow suspending in the last state
supported by the system.