Good evening, I have an up-to-date (daily updates) Arch system running Hyprland and since yesterday or the day before yesterday hibernation stopped working. Kernel version is 6.8.8-arch1-1 I have the following line in my hypridle.conf: listener { timeout = 1800 # 30min on-timeout = systemctl suspend-then-hibernate # suspend pc } This used to work flawlessly. When system is hibernating now it's crashing. This is the journal output: 9:27:11 systemd: Stopped target Bluetooth Support. 09:27:11 kernel: PM: hibernation: hibernation entry 09:27:11 systemd-sleep: Performing sleep operation 'hibernate'... 09:27:11 bluetoothd: Battery Provider Manager destroyed 09:27:11 systemd-sleep: System returned from sleep operation 'suspend- then-hibernate'. 09:27:11 bluetoothd: Endpoint unregistered: sender=:1.41 path=/MediaEndpoint/A2DPSink/aptx_hd 09:27:11 dbus-broker: A security policy denied :1.5 to send method call /midi/profile:org.blue z.GattProfile1.Release to :1.42. 09:27:11 bluetoothd: Endpoint unregistered: sender=:1.41 path=/MediaEndpoint/A2DPSource/ldac 09:27:11 kernel: PM: suspend exit 09:27:11 kernel: Bluetooth: hci0: Firmware Version: 132-3.24 09:27:11 kernel: done. 09:27:11 kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 09:27:11 kernel: Restarting tasks ... 09:27:11 kernel: OOM killer enabled. 09:27:11 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8 09:27:11 kernel: [drm] JPEG decode initialized successfully. 09:27:11 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully! 09:27:11 kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR 09:27:11 kernel: usb 1-4.4: reset full-speed USB device number 5 using xhci_hcd 09:27:11 kernel: ata2: SATA link down (SStatus 0 SControl 300) 09:27:11 kernel: ata1: SATA link down (SStatus 0 SControl 300) 09:27:11 kernel: nvme nvme0: 12/0/0 default/read/poll queues 09:27:11 kernel: [drm] PSP is resuming... 09:27:11 kernel: ACPI: EC: event unblocked 09:27:11 kernel: CPU15 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf 09:27:11 kernel: CPU14 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe 09:27:11 kernel: CPU13 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd 09:27:11 kernel: CPU12 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc 09:27:11 kernel: CPU11 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb 09:27:11 kernel: CPU10 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa 09:27:11 kernel: CPU9 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9 9:27:11 kernel: CPU9 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9 09:27:11 kernel: CPU8 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8 09:27:11 kernel: CPU7 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7 09:27:11 kernel: CPU6 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6 09:27:11 kernel: CPU5 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5 09:27:11 kernel: CPU4 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4 09:27:11 kernel: CPU3 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3 09:27:11 kernel: CPU2 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2 09:27:11 kernel: CPU1 is up 09:27:11 kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 09:27:11 kernel: Enabling non-boot CPUs ... 09:27:11 kernel: LVT offset 0 assigned for vector 0x400 09:27:11 kernel: AMD-Vi: Virtual APIC enabled 09:27:11 kernel: ACPI: PM: Restoring platform NVS memory 09:27:11 kernel: smpboot: CPU 15 is now offline 09:27:11 kernel: Spectre V2 : Update user space SMT mitigation: STIBP off 09:27:11 kernel: smpboot: CPU 14 is now offline 09:27:11 kernel: Disabling non-boot CPUs ... 09:27:11 kernel: ACPI: PM: Saving platform NVS memory 09:27:11 kernel: [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) 09:27:11 kernel: printk: Suspending console(s) (use no_console_suspend to debug) 09:27:11 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds) 09:27:11 kernel: OOM killer disabled. 09:27:11 kernel: Freezing user space processes completed (elapsed 0.001 seconds) 08:57:09 kernel: Filesystems sync: 0.006 seconds 08:57:09 kernel: PM: suspend entry (deep) 08:57:09 systemd-sleep: Performing sleep operation 'suspend'... 08:57:09 systemd: Starting System Suspend then Hibernate... Any idea what's going wrong here? THX Frank
On 24/05/01 05:24PM, Frank wrote:
Good evening,
Hey Frank,
I have an up-to-date (daily updates) Arch system running Hyprland and since yesterday or the day before yesterday hibernation stopped working. Kernel version is 6.8.8-arch1-1
Did you already try to downgrade the kernel or switch to the LTS version? If that changes anything it might be good to check with aur/linux-mainline if the issue is already fixed in mainline and if that is not the case to do a bisection on what causes the issue. Is the issue easily reproducible, i.e. does it happen every time you try to hibernate?
Any idea what's going wrong here? THX Frank
Cheers, gromit
Am Donnerstag, dem 02.05.2024 um 13:51 +0200 schrieb Christian Heusel:
On 24/05/01 05:24PM, Frank wrote:
Good evening,
Hey Frank,
Hi Christian,
I have an up-to-date (daily updates) Arch system running Hyprland and since yesterday or the day before yesterday hibernation stopped working. Kernel version is 6.8.8-arch1-1
Did you already try to downgrade the kernel or switch to the LTS version? If that changes anything it might be good to check with aur/linux-mainline if the issue is already fixed in mainline and if that is not the case to do a bisection on what causes the issue.
Yes it happens with LTS kernel as well. Actually, now that I installed the LTS kernel it might be that this is happening since the recent update of the mkinitcpio
Is the issue easily reproducible, i.e. does it happen every time you try to hibernate?
Yes, allways when systemctl hibernate is executed.
Any idea what's going wrong here? THX Frank
Cheers, gromit
Frank
Am Donnerstag, dem 02.05.2024 um 14:56 +0200 schrieb Frank:
Am Donnerstag, dem 02.05.2024 um 13:51 +0200 schrieb Christian Heusel:
I have an up-to-date (daily updates) Arch system running Hyprland and since yesterday or the day before yesterday hibernation stopped working.
Did you already try to downgrade the kernel or switch to the LTS version? If that changes anything it might be good to check with aur/linux-mainline if the issue is already fixed in mainline and if
Yes it happens with LTS kernel as well. Actually, now that I installed the LTS kernel it might be that this is happening since the recent update of the mkinitcpio
So it was the mkinitcpio update. When running etc-update, I missed the resume hook in the mkinitcpio.conf file. Now systems goes to hibernation and resumes a normally.
Frank
So it was the mkinitcpio update. When running etc-update, I missed the resume hook in the mkinitcpio.conf file. Now systems goes to hibernation and resumes a normally.
You can now put your custom HOOKS in /etc/mkinitcpio.conf.d/my-hooks.conf -- damjan
Am Donnerstag, dem 02.05.2024 um 19:48 +0200 schrieb Damjan Georgievski:
You can now put your custom HOOKS in /etc/mkinitcpio.conf.d/my- hooks.conf
Thanks for the tip. What would be the correct syntax? I put this HOOKS=(resume) in my /etc/mkinitcpio.conf.d/myhooks.conf but it's getting ignored.
participants (3)
-
Christian Heusel
-
Damjan Georgievski
-
Frank