I think hibernation was working for the last month but not if I close my laptop, which should then go to hibernation, it is still audibly running a few minutes later. Also using the hibernate option while the device is open, makes the screen go black for a few seconds and then show the login/lock screen.
I don’t think that I changed anything recently that would cause hibernation to no longer work and it seemed to have worked previously.
Pleas supply the output from inxi -zv8 post it using the </> button on the editor menu.
Until you provide the output of inxi -zv8 here is a little light reading on the topic.
Besides inxi, an fstab file here might contain relevant information.
The output of grep -i hooks /etc/mkinitcpio.conf will also be useful; I had the resume hook disappear from mine some time ago, for whatever mysterious reason.
It was Orcses, Preciousss. They comes here sometimes.
The Output of inxi -zv8:
System:
Kernel: 6.18.24-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
root=UUID=858f7022-23f6-49c3-8cbf-9956643da584 rw rootflags=subvol=@
quiet splash udev.log_priority=3
resume=UUID=858f7022-23f6-49c3-8cbf-9956643da584 resume_offset=21688691
Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A info: frameworks v: 6.25.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Convertible System: Dell product: Inspiron 16 7620 2-in-1 v: N/A
serial: <superuser required> Chassis: type: 31 serial: <superuser required>
Mobo: Dell model: 0FD3D2 v: A00 serial: <superuser required> part-nu: 0B37
uuid: <superuser required> Firmware: UEFI vendor: Dell v: 1.30.1
date: 09/09/2025
Battery:
ID-1: BAT0 charge: 6.2 Wh (8.9%) condition: 69.5/87 Wh (79.9%) health: good
temp: 28.3 C volts: 11.79 min: 11.4 model: SMP DELL 817GN98 made: 2022-04-21
type: Li-poly serial: <filter> charging: status: charging control:
start: 60% end: 80% type: custom
avail: adaptive,custom,fast,standard,trickle cycles: N/A
Memory:
System RAM: total: 16 GiB available: 15.3 GiB used: 4.3 GiB (28.1%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
max-module-size: 32 GiB note: est.
Device-1: DIMM 1 type: DDR4 detail: synchronous size: 8 GiB
speed: 3200 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: 80AD000080AD part-no: HMAA1GS6CJR6N-XN serial: <filter>
Device-2: DIMM 2 type: DDR4 detail: synchronous size: 8 GiB
speed: 3200 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: 80AD000080AD part-no: HMAA1GS6CJR6N-XN serial: <filter>
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: 12th Gen Intel Core i7-1260P bits: 64 type: MST AMCP
arch: Alder Lake level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 3
microcode: 0x43B
Topology: cpus: 1x dies: 1 clusters: 6 cores: 12 threads: 16 mt: 4 tpc: 2
st: 8 smt: enabled cache: L1: 1.1 MiB desc: d-8x32 KiB, 4x48 KiB; i-4x32
KiB, 8x64 KiB L2: 9 MiB desc: 4x1.2 MiB, 2x2 MiB L3: 18 MiB desc: 1x18 MiB
Speed (MHz): avg: 400 min/max: 400/4700:3400 scaling: driver: intel_pstate
governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400
8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 400
bogomips: 79872
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq pdcm
pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed
rdtscp rep_good sdbg sep serialize sha_ni smap smep smx split_lock_detect
ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc
tsc_adjust tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme vmx
vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt xsaves
xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: ghostwrite status: Not affected
...
Graphics:
Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: Dell
driver: i915 v: kernel arch: Xe process: Intel 10nm built: 2021-22+ ports:
active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 0000:00:02.0
chip-ID: 8086:46a6 class-ID: 0300
Device-2: NVIDIA TU117M [GeForce MX550] vendor: Dell driver: nvidia
v: 595.58.03 non-free: 550-580.xx+ status: current (as of 2025-11;
EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 bus-ID: 0000:01:00.0 chip-ID: 10de:1f9f class-ID: 0302
Device-3: Microdia Integrated_Webcam_FHD driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:3 chip-ID: 0c45:673f
class-ID: 0e02
Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: Samsung 0x4164 built: 2021 res: mode: 3840x2400
hz: 60 scale: 190% (1.9) to: 2021x1263 dpi: 284 gamma: 1.2 chroma: red:
x: 0.682 y: 0.322 green: x: 0.235 y: 0.725 blue: x: 0.137 y: 0.047 white:
x: 0.314 y: 0.329 size: 344x215mm (13.54x8.46") diag: 406mm (16")
ratio: 16:10 modes: 3840x2400
EDID-Warnings: 1: parse_edid: unknown flag 0
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 26.0.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Xe Graphics (ADL
GT2) device-ID: 8086:46a6 memory: 14.94 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.341 layers: 2 device: 0 type: discrete-gpu
name: NVIDIA GeForce MX550 driver: nvidia v: 595.58.03 device-ID: 10de:1f9f
surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo,xprop
Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Dell
driver: sof-audio-pci-intel-tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:51c8
class-ID: 0401
API: ALSA v: k6.18.24-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.6.4 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 0000:00:14.3 chip-ID: 8086:51f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
IF-ID-1: wg0-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
IP v4: <filter> scope: global broadcast: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0033
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Logical:
Message: No logical block device data found.
RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
Local Storage: total: 953.87 GiB used: 251.74 GiB (26.4%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: PM991a NVMe 1024GB size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 26304039 temp: 39.9 C scheme: GPT
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 488.28 GiB size: 488.28 GiB (100.00%)
used: 150.75 GiB (30.9%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
label: N/A uuid: 858f7022-23f6-49c3-8cbf-9956643da584
ID-2: /boot/efi raw-size: 200 MiB size: 196 MiB (98.00%)
used: 91.7 MiB (46.8%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
label: ESP uuid: 7459-6D7E
ID-3: /home raw-size: 488.28 GiB size: 488.28 GiB (100.00%)
used: 150.75 GiB (30.9%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
label: N/A uuid: 858f7022-23f6-49c3-8cbf-9956643da584
ID-4: /home/<filter>/ ...
ID-5: /swap raw-size: 488.28 GiB size: 488.28 GiB (100.00%)
used: 150.75 GiB (30.9%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
label: N/A uuid: 858f7022-23f6-49c3-8cbf-9956643da584
ID-6: /var/cache raw-size: 488.28 GiB size: 488.28 GiB (100.00%)
used: 150.75 GiB (30.9%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
label: N/A uuid: 858f7022-23f6-49c3-8cbf-9956643da584
ID-7: /var/log raw-size: 488.28 GiB size: 488.28 GiB (100.00%)
used: 150.75 GiB (30.9%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
label: N/A uuid: 858f7022-23f6-49c3-8cbf-9956643da584
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: file size: 20 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Unmounted:
ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 128 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 444.59 GiB fs: ntfs label: OS
uuid: A4D29308D292DE3C
ID-3: /dev/nvme0n1p4 maj-min: 259:4 size: 1.09 GiB fs: ntfs label: N/A
uuid: 76EA9B9CEA9B56E9
ID-4: /dev/nvme0n1p5 maj-min: 259:5 size: 18.14 GiB fs: ntfs label: Image
uuid: 8664431964430AFF
ID-5: /dev/nvme0n1p6 maj-min: 259:6 size: 1.43 GiB fs: ntfs
label: DELLSUPPORT uuid: 06E4D2BFE4D2B063
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-2: 2-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 3-5:2 info: Shenzhen Goodix USB2.0 MISC type: <vendor specific>
driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
mode: 1.1 power: 100mA chip-ID: 27c6:639c class-ID: ef00 serial: <filter>
Device-2: 3-6:3 info: Microdia Integrated_Webcam_FHD type: video
driver: uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 power: 500mA chip-ID: 0c45:673f class-ID: 0e02
Device-3: 3-10:4 info: Intel AX211 Bluetooth type: bluetooth driver: btusb
interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
power: 100mA chip-ID: 8087:0033 class-ID: e001
Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 52.0 C mobo: 48.0 C sodimm: 48.0 C
Fan Speeds (rpm): cpu: 2608
Repos:
Packages: 1392 pm: pacman pkgs: 1382 libs: 373 tools: pamac pm: flatpak
pkgs: 10
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/testing/$repo/$arch
2: https://mirror.2degrees.nz/manjaro/testing/$repo/$arch
3: https://ct.mirror.garr.it/mirrors/manjaro/testing/$repo/$arch
... I don't think these are all required
74: https://nnenix.mm.fcix.net/manjaro/testing/$repo/$arch
75: https://mirror.fcix.net/manjaro/testing/$repo/$arch
76: https://kartolo.sby.datautama.net.id/manjaro/testing/$repo/$arch
Processes:
CPU top: 5 of 387
1: cpu: 11.9% command: firefox pid: 3000 mem: 765.1 MiB (4.8%)
...
Memory top: 5 of 387
1: mem: 765.1 MiB (4.8%) command: firefox pid: 3000 cpu: 11.9%
...
Info:
Processes: 387 Power: uptime: 7m states: freeze,mem,disk suspend: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 6.02 GiB services: org_kde_powerdevil, power-profiles-daemon,
upowerd Init: systemd v: 260 default: graphical tool: systemctl
Compilers: clang: 22.1.3 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
inxi: 3.3.40
Parts I have removed are marked with “…”
Mod Edit: Fixed formatting
I should also mention that I have tried some things and currently the systems pretends to hibernate but at the same time managed to lose 80%(until empty) battery in under 24 hours while it should have been in hibernation
I get HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth filesystems resume)
resume seems to be present
I have been on the mentioned arch wiki site already, that’s how I got it to a place where it was running, or so I think, sometime ago
If I didn’t miss anything the second page is general information about sleep states which I roughly knew but not in the detail provided here
When checking what exactly my Power Management settings where I discovered The action you had previously configured for when the lid is closed is now unsupported on your system. Please select a different one. where I had previously set it to hibernate
Mod edit: Merged consecutive posts. Please use the Edit feature to add more information. 
resume needs to come directly after udev, if you use the udev hook.
But a Manjaro pacnew should have switched you to systemd.
You pick left or right in this table of sequential hooks:
Not necessarily. Is not logical but it works (i was with that setup) and even the wiki puts resume at the end. This is not the problem.
Actually, I assumed that the resume hook being missing (or in the wrong place?) wouldn’t affect a hibernation attempt, just prevent a resume from such from working; in my case, waking the machine gave a clean boot instead of resuming? (No power drain, that I noticed).
No, a .pacnew is advisory only. It does not automatically take the place of an already existing and presumably customized configuration file. That’s the whole point of .pacnew files.
I need to stop replying on my phone. (Of course I know that!)
I meant you would have seen the defaults have changed in the pacnew file. (The commented out lines.)
Then the patch notes even explained how to switch. (Among the dozens of posts around and after that time for people that didn’t read it.)
I switched because of the mkinitcpio.conf.pacnew file. It obviously didn’t switch it for me.
If you can confirm when you last hibernated successfully (if your system log goes back that far - journalctl --grep "hibernat")
Then check your pacman logs to see what has been installed/upgraded since then cat /var/log/pacman.log | grep -i "installed\|upgraded"
Check for any *.pacnew files you haven’t processed pacdiff -o
Put all of that together and see what potentially broke hibernation. If you still don’t get an answer, you can work through the kernel power hibernation/suspend debugging.
I got the following as the most recent hit there.
-- Boot f6b072ddc8414d7d918453b539ab22d2 --
Apr 30 10:29:45 inspiron16 kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Apr 30 10:29:45 inspiron16 kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
Apr 30 10:29:45 inspiron16 kernel: PM: hibernation: Registered nosave memory: [mem 0x575b1000-0x57639fff]
Apr 30 10:29:45 inspiron16 kernel: PM: hibernation: Registered nosave memory: [mem 0x5cd1e000-0x617fefff]
Apr 30 10:29:45 inspiron16 kernel: PM: hibernation: Registered nosave memory: [mem 0x61800000-0xffffffff]
Apr 30 10:29:45 inspiron16 systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
Apr 30 10:29:47 inspiron16 systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
Apr 30 10:29:47 inspiron16 systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
Apr 30 10:29:47 inspiron16 systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
Apr 30 10:33:35 inspiron16 systemd-logind[698]: The system will hibernate now!
Apr 30 10:33:35 inspiron16 systemd[1]: Starting NVIDIA system hibernate actions...
Apr 30 10:33:35 inspiron16 systemd[1]: nvidia-hibernate.service: Skipped due to 'exec-condition'.
Apr 30 10:33:35 inspiron16 systemd[1]: Condition check resulted in NVIDIA system hibernate actions being skipped.
Apr 30 10:33:35 inspiron16 systemd[1]: Starting System Hibernate...
Apr 30 10:33:35 inspiron16 systemd-sleep[3283]: in suspend-then-hibernate operations or setups with encrypted home directories.
Apr 30 10:33:35 inspiron16 systemd-sleep[3283]: Performing sleep operation 'hibernate'...
Apr 30 10:33:35 inspiron16 kernel: PM: hibernation: hibernation entry
Apr 30 10:33:56 inspiron16 kernel: PM: hibernation: hibernation exit
Apr 30 10:33:56 inspiron16 systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE
Apr 30 10:33:56 inspiron16 systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
Apr 30 10:33:56 inspiron16 systemd[1]: Failed to start System Hibernate.
Apr 30 10:33:56 inspiron16 systemd[1]: Dependency failed for System Hibernation.
Apr 30 10:33:56 inspiron16 systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.
Apr 30 10:33:56 inspiron16 systemd[1]: systemd-hibernate.service: Consumed 2.377s CPU time over 21.132s wall clock time, 11.8M memory peak.
Apr 30 10:33:56 inspiron16 systemd-logind[698]: Operation 'hibernate' finished.
Apr 30 10:36:16 inspiron16 systemd-logind[698]: The system will hibernate now!
Apr 30 10:36:16 inspiron16 systemd[1]: Starting NVIDIA system hibernate actions...
Apr 30 10:36:16 inspiron16 systemd[1]: nvidia-hibernate.service: Skipped due to 'exec-condition'.
Apr 30 10:36:16 inspiron16 systemd[1]: Condition check resulted in NVIDIA system hibernate actions being skipped.
Apr 30 10:36:16 inspiron16 systemd[1]: Starting System Hibernate...
Apr 30 10:36:16 inspiron16 systemd-sleep[3696]: in suspend-then-hibernate operations or setups with encrypted home directories.
Apr 30 10:36:16 inspiron16 systemd-sleep[3696]: Performing sleep operation 'hibernate'...
Apr 30 10:36:16 inspiron16 kernel: PM: hibernation: hibernation entry
Apr 30 10:36:37 inspiron16 kernel: PM: hibernation: hibernation exit
Apr 30 10:36:37 inspiron16 systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE
Apr 30 10:36:37 inspiron16 systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
Apr 30 10:36:37 inspiron16 systemd[1]: Failed to start System Hibernate.
Apr 30 10:36:37 inspiron16 systemd[1]: Dependency failed for System Hibernation.
Apr 30 10:36:37 inspiron16 systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.
Apr 30 10:36:37 inspiron16 systemd[1]: systemd-hibernate.service: Consumed 2.375s CPU time over 21.141s wall clock time, 12.1M memory peak.
Apr 30 10:36:37 inspiron16 systemd-logind[698]: Operation 'hibernate' finished.
Right after this the device directly wakes up again on the login/lock screen.
As I don’t know which of the hibernations actually worked, I don’t know when to look back to. Is there anything in particular that I should keep an eye out for?
This doesn’t give an output
I have now switched to
HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
which was already present as a comment in the conf file and seems to be what the wiki says aswell.
I will look into this more detailed when I have a bit more time
You’ll need to interrogate the log in more detail around these entries, but we know the hibernation is failing because it says so. Likely a process is not freezing in time, or a device may not be configured to hibernate due to power settings.
But we’re looking for the last time you hibernated sucessfully so we can work out what changed to stop it.
That’s why we check the logs, to find out.
A successful hibernation entry, followed a significant time later when it restored from hibernation. You could try journalctl --grep "hibernate.target" to reduce some of the superfluous entries but once you find it you’ll need to get the date and time of the successful hibernation then check pacman logs since that date/time to see what has changed.
My bad, I didn’t give you the full command. Try pacdiff --find -o or pacdiff --locate -o. If you’ve dealt with pacsave files each time you’ve upgraded you may not have any (this is good).
I have looked into the logs now just after trying to hibernate, where the screen then turns off shortly and puts me back on the login/lock screen. It appears to be a process not freezing. The full system logs in this timespan are:
Apr 30 10:53:53 inspiron16 kernel: Filesystems sync: 0.016 seconds
Apr 30 10:54:13 inspiron16 kernel: Freezing user space processes
Apr 30 10:54:13 inspiron16 kernel: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 30 10:54:13 inspiron16 kernel: task:Thread (pooled) state:D stack:0 pid:1217 tgid:1046 ppid:946 task_flags:0x400040 flags:0x00080003
Apr 30 10:54:13 inspiron16 kernel: Call Trace:
Apr 30 10:54:13 inspiron16 kernel: <TASK>
Apr 30 10:54:13 inspiron16 kernel: __schedule+0x418/0x1320
Apr 30 10:54:13 inspiron16 kernel: schedule+0x27/0xd0
Apr 30 10:54:13 inspiron16 kernel: request_wait_answer+0xce/0x290
Apr 30 10:54:13 inspiron16 kernel: ? __pfx_autoremove_wake_function+0x10/0x10
Apr 30 10:54:13 inspiron16 kernel: ? __pfx_fuse_dir_open+0x10/0x10
Apr 30 10:54:13 inspiron16 kernel: __fuse_simple_request+0x120/0x320
Apr 30 10:54:13 inspiron16 kernel: fuse_send_open+0xb6/0x120
Apr 30 10:54:13 inspiron16 kernel: ? fuse_file_alloc+0xb2/0xe0
Apr 30 10:54:13 inspiron16 kernel: ? __kmalloc_cache_noprof+0x483/0x5c0
Apr 30 10:54:13 inspiron16 kernel: fuse_file_open+0xe7/0x1c0
Apr 30 10:54:13 inspiron16 kernel: fuse_do_open+0x18/0x30
Apr 30 10:54:13 inspiron16 kernel: fuse_dir_open+0x62/0xb0
Apr 30 10:54:13 inspiron16 kernel: do_dentry_open+0x240/0x480
Apr 30 10:54:13 inspiron16 kernel: vfs_open+0x30/0x100
Apr 30 10:54:13 inspiron16 kernel: path_openat+0x7ea/0x12e0
Apr 30 10:54:13 inspiron16 kernel: ? switch_fpu_return+0x4e/0xd0
Apr 30 10:54:13 inspiron16 kernel: do_filp_open+0xd8/0x180
Apr 30 10:54:13 inspiron16 kernel: ? __x64_sys_getdents64+0xed/0x110
Apr 30 10:54:13 inspiron16 kernel: ? alloc_fd+0x12e/0x190
Apr 30 10:54:13 inspiron16 kernel: do_sys_openat2+0x88/0xe0
Apr 30 10:54:13 inspiron16 kernel: ? autoremove_wake_function+0x16/0x70
Apr 30 10:54:13 inspiron16 kernel: __x64_sys_openat+0x61/0xa0
Apr 30 10:54:13 inspiron16 kernel: do_syscall_64+0x81/0x7d0
Apr 30 10:54:13 inspiron16 kernel: ? kmem_cache_free+0x528/0x5d0
Apr 30 10:54:13 inspiron16 kernel: ? __x64_sys_close+0x3d/0x80
Apr 30 10:54:13 inspiron16 kernel: ? __x64_sys_close+0x3d/0x80
Apr 30 10:54:13 inspiron16 kernel: ? do_syscall_64+0x81/0x7d0
Apr 30 10:54:13 inspiron16 kernel: ? sched_clock_cpu+0xf/0x200
Apr 30 10:54:13 inspiron16 kernel: ? __rseq_handle_notify_resume+0xa6/0x4b0
Apr 30 10:54:13 inspiron16 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Apr 30 10:54:13 inspiron16 kernel: RIP: 0033:0x7f394270e076
Apr 30 10:54:13 inspiron16 kernel: RSP: 002b:00007f393d5fd260 EFLAGS: 00000206 ORIG_RAX: 0000000000000101
Apr 30 10:54:13 inspiron16 kernel: RAX: ffffffffffffffda RBX: 00007ef9300115e0 RCX: 00007f394270e076
Apr 30 10:54:13 inspiron16 kernel: RDX: 0000000000090800 RSI: 00007ef930022600 RDI: 00000000ffffff9c
Apr 30 10:54:13 inspiron16 kernel: RBP: 00007f393d5fd2b0 R08: 00000000000000b0 R09: 80cb60ee5e2d4466
Apr 30 10:54:13 inspiron16 kernel: R10: 0000000000000000 R11: 0000000000000206 R12: 00007ef930001a60
Apr 30 10:54:13 inspiron16 kernel: R13: 00007ef9300018f8 R14: 00007ef9300018f8 R15: 00007ef9300115e0
Apr 30 10:54:13 inspiron16 kernel: </TASK>
Apr 30 10:54:13 inspiron16 kernel: OOM killer enabled.
Apr 30 10:54:13 inspiron16 kernel: Restarting tasks: Starting
Apr 30 10:54:13 inspiron16 kernel: Restarting tasks: Done
Apr 30 10:54:13 inspiron16 kernel: efivarfs: resyncing variable state
Apr 30 10:54:13 inspiron16 kernel: efivarfs: finished resyncing variable state
Apr 30 10:54:13 inspiron16 kernel: PM: hibernation: hibernation exit
Apr 30 10:54:13 inspiron16 systemd-sleep[4224]: Failed to put system to sleep. System resumed again: Device or resource busy
Apr 30 10:54:13 inspiron16 systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE
Apr 30 10:54:13 inspiron16 systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
Apr 30 10:54:13 inspiron16 systemd[1]: Failed to start System Hibernate.
Apr 30 10:54:13 inspiron16 systemd[1]: Dependency failed for System Hibernation.
Apr 30 10:54:13 inspiron16 systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.
Apr 30 10:54:13 inspiron16 systemd[1]: systemd-hibernate.service: Consumed 2.378s CPU time over 21.126s wall clock time, 11.9M memory peak.
All the entries that show up with the given command all have the same message:
hibernate.target: Job hibernate.target/start failed with result 'dependency'.
I assume this means that I never had hibernation working and just assumed that it did
--find -o has no output while --locate -o gives me:
/var/lib/plocate/plocate.db: Short read (file corrupted?)
/var/lib/plocate/plocate.db: Short read (file corrupted?)
/var/lib/plocate/plocate.db: Short read (file corrupted?)
/var/lib/plocate/plocate.db: Short read (file corrupted?)
I have never looked at pacsave files so far, does pacman/paman automatically handle any of this?
Likely; or your logs don’t go back far enough.
No, it’s an additional task that should be done after every upgrade. Although you can add a hook to run pacdiff every time you upgrade with pacman.
Make sure you’re familiar with how diff works and vi too probably (the editor may be different on your machine) if you setup the hook above. Otherwise after every upgrade you can simply run pacdiff --find -o and it will give you a list of pacsave files you need to compare with the same file (without .pacsave) on your system and work out what changes to keep or discard depending on what you have configured.
But I suggest you get familiar with how it works first. There are a number of threads on this forum that have good discussion on the topic.
Here for example: Check and manage pacnew files
No output from --find likely means you don’t have any pacnew files to worry about (good). That output from --locate likely means you haven’t got locate configured.
Correct. But the log isn’t listing the process for some reason (it usually does). It does provide a process ID though, so next time you try it immediately after it fails. Run ps -q [PID] (replace [PID] with the PID listed in the kernel: task:Thread entry to work out which process is holding things up.
They mean .pacnew files, which contain new default config when the default has been modified by the user. As already mentioned it’s a manual process.
.pacsave files are left when you uninstall something (using -R) and you’ve changed the default config. If you want to remove the config too then you can use -Rn.
It will list both .pacnew and .pacsave files.
If i understand correctly you didn’t really shut down…and the process didn’t freeze…so maybe this process is still there and not killed? A bit of a shot in the dark but worth checking if process 1217 exists and what is it. Or you can try hibernating 2 times and see if the process id in the log changes.
Actually, pacdiff -o is what I use and it works fine. In fact, I see I have a few .pacnews to tend to.