Good morning Markku,

After trying to wake up the laptop from sleep, does the blinking LED stop blinking, or does it continue to blink without reacting? 
As for hibernation, make sure you have enough Swap space allocated for it to hibernate properly, hibernation might work with less space allocated than RAM in the device, but not always

Has this only happened recently, or it always happened after getting the laptop? I also suggest messing around with older kernels if possible and see if the issue goes away

Looking forward for your reply,

Regards,

Hello, thank your for your reply!

On suspend, the power button LED continues to blink without reacting when pressing the power button.

For the hibernation, I should have enough swap. I have swap: 102400.00 MiB  and memory I have : 63403.63 MiB.

So the first time I hibernate, it works. But if I hibernate second time, it tries to hibernate, screen goes blank, it continues to process and eventually will boot. I'll check next time, that there is enough free SWAP before hibernating. If the hibernation swap is not freed, it could explain it.

I think both of these issues have been present the whole time I have had the EVO laptop (December 2025).

Here is logs for successful and unsuccessful hibernations, they seem quite similar. 

Successful hibernation:

Jan 05 16:36:50 hai0620 systemd-logind[3076]: The system will hibernate now!
Jan 05 16:36:50 hai0620 NetworkManager[3198]: <info>  [1767623810.7663] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 05 16:36:50 hai0620 ModemManager[3170]: <msg> [sleep-monitor-systemd] system is about to suspend
Jan 05 16:36:50 hai0620 NetworkManager[3198]: <info>  [1767623810.7667] device (p2p-dev-wlp99s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 05 16:36:50 hai0620 ModemManager[3170]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Jan 05 16:36:50 hai0620 NetworkManager[3198]: <info>  [1767623810.7669] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 05 16:36:50 hai0620 NetworkManager[3198]: <info>  [1767623810.7670] device (wlp99s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 05 16:36:50 hai0620 kwin_wayland[3935]: Failed to delay sleep: The operation inhibition has been requested for is already running
Jan 05 16:36:50 hai0620 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 05 16:36:50 hai0620 systemd[1]: Starting PackageKit Daemon...
Jan 05 16:36:50 hai0620 systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 05 16:36:50 hai0620 PackageKit[15067]: daemon start
Jan 05 16:36:50 hai0620 kernel: wlp99s0: deauthenticating from 46:7c:70:42:20:8b by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 05 16:36:50 hai0620 systemd[1]: Started PackageKit Daemon.
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.0932] device (wlp99s0): supplicant interface state: completed -> disconnected
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.0933] device (wlp99s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Withdrawing address record for fe80::fa3d:c6ff:fe0c:1ebc on wlp99s0.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Leaving mDNS multicast group on interface wlp99s0.IPv6 with address fe80::fa3d:c6ff:fe0c:1ebc.
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.0937] dhcp4 (wlp99s0): canceled DHCP transaction
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Interface wlp99s0.IPv6 no longer relevant for mDNS.
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.0937] dhcp4 (wlp99s0): activation: beginning transaction (timeout in 45 seconds)
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.0937] dhcp4 (wlp99s0): state changed no lease
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Interface wlp99s0.IPv4 no longer relevant for mDNS.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Leaving mDNS multicast group on interface wlp99s0.IPv4 with address 192.168.9.229.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Withdrawing address record for 192.168.9.229 on wlp99s0.
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.1533] device (wlp99s0): set-hw-addr: set MAC address to 32:E8:34:66:48:1D (scanning)
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Joining mDNS multicast group on interface wlp99s0.IPv4 with address 192.168.9.229.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: New relevant interface wlp99s0.IPv4 for mDNS.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Registering new address record for 192.168.9.229 on wlp99s0.IPv4.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Withdrawing address record for 192.168.9.229 on wlp99s0.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Leaving mDNS multicast group on interface wlp99s0.IPv4 with address 192.168.9.229.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Interface wlp99s0.IPv4 no longer relevant for mDNS.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: Files changed, reloading.
Jan 05 16:36:51 hai0620 avahi-daemon[3055]: No service file found in /etc/avahi/services.
Jan 05 16:36:51 hai0620 dnsmasq[3745]: reading /etc/resolv.conf
Jan 05 16:36:51 hai0620 dnsmasq[3745]: using nameserver 192.168.101.1#53
Jan 05 16:36:51 hai0620 dnsmasq[3745]: using only locally-known addresses for incus
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.2057] device (wlp99s0): supplicant interface state: disconnected -> interface_disabled
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.2057] device (wlp99s0): supplicant interface state: interface_disabled -> disconnected
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.2061] device (wlp99s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 05 16:36:51 hai0620 dns-dnsmasq.sh[15151]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Jan 05 16:36:51 hai0620 NetworkManager[3198]: <info>  [1767623811.2646] device (wlp99s0): set-hw-addr: reset MAC address to F8:3D:C6:0C:1E:BC (unmanage)
Jan 05 16:36:51 hai0620 systemd[1]: Reached target Sleep.
Jan 05 16:36:51 hai0620 systemd[1]: Starting System Hibernate...
Jan 05 16:36:51 hai0620 dns-dnsmasq.sh[15167]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Jan 05 16:36:51 hai0620 systemd[1]: user@1001.service: Unit now frozen-by-parent.
Jan 05 16:36:51 hai0620 systemd[1]: session-3.scope: Unit now frozen-by-parent.
Jan 05 16:36:51 hai0620 systemd[1]: user.slice: Unit now frozen.
Jan 05 16:36:51 hai0620 systemd[1]: user-1001.slice: Unit now frozen-by-parent.
Jan 05 16:36:51 hai0620 systemd-sleep[15162]: Successfully froze unit 'user.slice'.
Jan 05 16:36:51 hai0620 systemd-sleep[15178]: storing slimbook configuration:
Jan 05 16:36:51 hai0620 systemd-sleep[15175]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for bootloader: grub2-bls
Jan 05 16:36:51 hai0620 systemd-sleep[15178]: 0
Jan 05 16:36:51 hai0620 systemd-sleep[15162]: Performing sleep operation 'hibernate'...
Jan 05 16:36:51 hai0620 kernel: PM: hibernation: hibernation entry
Jan 05 16:36:51 hai0620 kernel: Filesystems sync: 0.010 seconds

Jan 06 13:05:29 hai0620 kernel: Freezing user space processes
Jan 06 13:05:29 hai0620 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jan 06 13:05:29 hai0620 kernel: OOM killer disabled.
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x000a0000-0x000fffff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x09a7f000-0x09ffffff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x0a200000-0x0a23bfff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x62898000-0x629f7fff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x62bb4000-0x62bb4fff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x67f7f000-0x781fefff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x79ff7000-0x79ffcfff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Marking nosave pages: [mem 0x79fff000-0xffffffff]
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Basic memory bitmaps created
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Preallocating image memory
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Allocated 4063382 pages for snapshot
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Allocated 16253528 kbytes in 0.58 seconds (28023.32 MB/s)
Jan 06 13:05:29 hai0620 kernel: Freezing remaining freezable tasks
Jan 06 13:05:29 hai0620 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Jan 06 13:05:29 hai0620 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 06 13:05:29 hai0620 kernel: queueing ieee80211 work while going to suspend
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: Register(0) [regVPEC_QUEUE_RESET_REQ] failed to reach value 0x00000000 != 0x00000001n
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: VPE queue reset failed
Jan 06 13:05:29 hai0620 kernel: ACPI: EC: interrupt blocked
Jan 06 13:05:29 hai0620 kernel: ACPI: PM: Preparing to enter system sleep state S4
Jan 06 13:05:29 hai0620 kernel: ACPI: EC: event blocked
Jan 06 13:05:29 hai0620 kernel: ACPI: EC: EC stopped
Jan 06 13:05:29 hai0620 kernel: ACPI: PM: Saving platform NVS memory
Jan 06 13:05:29 hai0620 kernel: Disabling non-boot CPUs ...
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 19 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 18 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 17 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 16 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 15 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 14 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 13 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 12 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 11 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 10 is now offline
Jan 06 13:05:29 hai0620 kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 9 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 8 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 7 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 6 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 5 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 4 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 3 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 2 is now offline
Jan 06 13:05:29 hai0620 kernel: smpboot: CPU 1 is now offline
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Creating image:
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Need to copy 4187597 pages
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Normal pages needed: 4187597 + 1024, available pages: 12356459
Jan 06 13:05:29 hai0620 kernel: ACPI: PM: Restoring platform NVS memory
Jan 06 13:05:29 hai0620 kernel: ACPI: EC: EC started
Jan 06 13:05:29 hai0620 kernel: AMD-Vi: Virtual APIC enabled
Jan 06 13:05:29 hai0620 kernel: AMD-Vi: Virtual APIC enabled
Jan 06 13:05:29 hai0620 kernel: LVT offset 0 assigned for vector 0x400
Jan 06 13:05:29 hai0620 kernel: Enabling non-boot CPUs ...
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 06 13:05:29 hai0620 kernel: CPU1 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jan 06 13:05:29 hai0620 kernel: CPU2 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jan 06 13:05:29 hai0620 kernel: CPU3 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x10
Jan 06 13:05:29 hai0620 kernel: CPU4 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 5 APIC 0x12
Jan 06 13:05:29 hai0620 kernel: CPU5 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x14
Jan 06 13:05:29 hai0620 kernel: CPU6 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x16
Jan 06 13:05:29 hai0620 kernel: CPU7 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x18
Jan 06 13:05:29 hai0620 kernel: CPU8 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x1a
Jan 06 13:05:29 hai0620 kernel: CPU9 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 10 APIC 0x1
Jan 06 13:05:29 hai0620 kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Jan 06 13:05:29 hai0620 kernel: CPU10 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 11 APIC 0x3
Jan 06 13:05:29 hai0620 kernel: CPU11 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 12 APIC 0x5
Jan 06 13:05:29 hai0620 kernel: CPU12 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 13 APIC 0x7
Jan 06 13:05:29 hai0620 kernel: CPU13 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 14 APIC 0x11
Jan 06 13:05:29 hai0620 kernel: CPU14 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 15 APIC 0x13
Jan 06 13:05:29 hai0620 kernel: CPU15 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 16 APIC 0x15
Jan 06 13:05:29 hai0620 kernel: CPU16 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 17 APIC 0x17
Jan 06 13:05:29 hai0620 kernel: CPU17 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 18 APIC 0x19
Jan 06 13:05:29 hai0620 kernel: CPU18 is up
Jan 06 13:05:29 hai0620 kernel: smpboot: Booting Node 0 Processor 19 APIC 0x1b
Jan 06 13:05:29 hai0620 kernel: CPU19 is up
Jan 06 13:05:29 hai0620 kernel: ACPI: PM: Waking up from system sleep state S4
Jan 06 13:05:29 hai0620 kernel: ACPI: button: The lid device is not compliant to SW_LID.
Jan 06 13:05:29 hai0620 kernel: ACPI: EC: interrupt unblocked
Jan 06 13:05:29 hai0620 kernel: ACPI: EC: event unblocked
Jan 06 13:05:29 hai0620 kernel: usb usb1: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: usb usb2: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: usb usb3: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: usb usb4: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: usb usb5: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: usb usb7: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: usb usb6: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: usb usb8: root hub lost power or was reset
Jan 06 13:05:29 hai0620 kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FB00000).
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: PSP is resuming...
Jan 06 13:05:29 hai0620 kernel: yt6801 0000:64:00.0 eno1: 1 Tx hardware queues,
Jan 06 13:05:29 hai0620 kernel: yt6801 0000:64:00.0 eno1:  8192 byte fifo per queue
Jan 06 13:05:29 hai0620 kernel: yt6801 0000:64:00.0 eno1: 4 Rx hardware queues,
Jan 06 13:05:29 hai0620 kernel: yt6801 0000:64:00.0 eno1:  8192 byte fifo per queue
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: reserve 0x8900000 from 0x8010000000 for PSP TMR
Jan 06 13:05:29 hai0620 kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jan 06 13:05:29 hai0620 kernel: nvme nvme1: 16/0/0 default/read/poll queues
Jan 06 13:05:29 hai0620 kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
Jan 06 13:05:29 hai0620 kernel: usb 3-1: reset high-speed USB device number 2 using xhci_hcd
Jan 06 13:05:29 hai0620 kernel: usb 3-5: reset high-speed USB device number 3 using xhci_hcd
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: RAP: optional rap ta ucode is not available
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: SMU is resuming...
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: SMU is resumed successfully!
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x09003600
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring jpeg_dec_0 uses VM inv eng 1 on hub 8
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ring vpe uses VM inv eng 4 on hub 8
Jan 06 13:05:29 hai0620 kernel: usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on vpe (-110).
Jan 06 13:05:29 hai0620 kernel: amdgpu 0000:66:00.0: amdgpu: ib ring test failed (-110).
Jan 06 13:05:29 hai0620 kernel: mt7921e 0000:63:00.0: Message 00020007 (seq 14) timeout
Jan 06 13:05:29 hai0620 kernel: mt7921e 0000:63:00.0: PM: dpm_run_callback(): pci_pm_restore returns -110
Jan 06 13:05:29 hai0620 kernel: mt7921e 0000:63:00.0: PM: failed to restore async: error -110
Jan 06 13:05:29 hai0620 kernel: mt7921e 0000:63:00.0: HW/SW Version: 0x8a108a10, Build Time: 20251118163143a
Jan 06 13:05:29 hai0620 kernel: mt7921e 0000:63:00.0: WM Firmware Version: ____000000, Build Time: 20251118163234
Jan 06 13:05:29 hai0620 kernel: wlp99s0: Driver requested disconnection from AP 00:00:00:00:00:00
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: Basic memory bitmaps freed
Jan 06 13:05:29 hai0620 kernel: OOM killer enabled.
Jan 06 13:05:29 hai0620 kernel: Restarting tasks: Starting
Jan 06 13:05:29 hai0620 kernel: Restarting tasks: Done
Jan 06 13:05:29 hai0620 kernel: efivarfs: resyncing variable state
Jan 06 13:05:29 hai0620 kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
Jan 06 13:05:29 hai0620 kernel: efivarfs: finished resyncing variable state
Jan 06 13:05:29 hai0620 kernel: PM: hibernation: hibernation exit

unsuccessful hibernation:

Jan 06 13:11:51 hai0620 systemd-logind[3076]: The system will hibernate now!
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.4067] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 06 13:11:51 hai0620 ModemManager[3170]: <msg> [sleep-monitor-systemd] system is about to suspend
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.4070] device (p2p-dev-wlp99s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 06 13:11:51 hai0620 ModemManager[3170]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.4073] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.4074] device (wlp99s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 06 13:11:51 hai0620 kwin_wayland[3935]: Failed to delay sleep: The operation inhibition has been requested for is already running
Jan 06 13:11:51 hai0620 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 06 13:11:51 hai0620 systemd[1]: Starting PackageKit Daemon...
Jan 06 13:11:51 hai0620 PackageKit[16325]: daemon start
Jan 06 13:11:51 hai0620 systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 06 13:11:51 hai0620 kernel: wlp99s0: deauthenticating from 46:7c:70:42:20:8b by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 06 13:11:51 hai0620 systemd[1]: Started PackageKit Daemon.
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.7248] device (wlp99s0): supplicant interface state: completed -> disconnected
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.7250] device (wlp99s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Withdrawing address record for fe80::fa3d:c6ff:fe0c:1ebc on wlp99s0.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Leaving mDNS multicast group on interface wlp99s0.IPv6 with address fe80::fa3d:c6ff:fe0c:1ebc.
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.7254] dhcp4 (wlp99s0): canceled DHCP transaction
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Interface wlp99s0.IPv6 no longer relevant for mDNS.
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.7254] dhcp4 (wlp99s0): activation: beginning transaction (timeout in 45 seconds)
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.7254] dhcp4 (wlp99s0): state changed no lease
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Interface wlp99s0.IPv4 no longer relevant for mDNS.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Leaving mDNS multicast group on interface wlp99s0.IPv4 with address 192.168.9.229.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Withdrawing address record for 192.168.9.229 on wlp99s0.
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.7857] device (wlp99s0): set-hw-addr: set MAC address to F2:71:33:CE:3D:19 (scanning)
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Joining mDNS multicast group on interface wlp99s0.IPv4 with address 192.168.9.229.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: New relevant interface wlp99s0.IPv4 for mDNS.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Registering new address record for 192.168.9.229 on wlp99s0.IPv4.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Withdrawing address record for 192.168.9.229 on wlp99s0.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Leaving mDNS multicast group on interface wlp99s0.IPv4 with address 192.168.9.229.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Interface wlp99s0.IPv4 no longer relevant for mDNS.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: Files changed, reloading.
Jan 06 13:11:51 hai0620 avahi-daemon[3055]: No service file found in /etc/avahi/services.
Jan 06 13:11:51 hai0620 dnsmasq[3745]: reading /etc/resolv.conf
Jan 06 13:11:51 hai0620 dnsmasq[3745]: using nameserver 192.168.101.1#53
Jan 06 13:11:51 hai0620 dnsmasq[3745]: using only locally-known addresses for incus
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.8463] device (wlp99s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 06 13:11:51 hai0620 dns-dnsmasq.sh[16395]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Jan 06 13:11:51 hai0620 NetworkManager[3198]: <info>  [1767697911.9025] device (wlp99s0): set-hw-addr: reset MAC address to F8:3D:C6:0C:1E:BC (unmanage)
Jan 06 13:11:51 hai0620 systemd[1]: Reached target Sleep.
Jan 06 13:11:51 hai0620 systemd[1]: Starting System Hibernate...
Jan 06 13:11:51 hai0620 dns-dnsmasq.sh[16426]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Jan 06 13:11:51 hai0620 systemd[1]: user@1001.service: Unit now frozen-by-parent.
Jan 06 13:11:51 hai0620 systemd[1]: session-3.scope: Unit now frozen-by-parent.
Jan 06 13:11:51 hai0620 systemd[1]: user-1001.slice: Unit now frozen-by-parent.
Jan 06 13:11:51 hai0620 systemd[1]: user.slice: Unit now frozen.
Jan 06 13:11:51 hai0620 systemd-sleep[16421]: Successfully froze unit 'user.slice'.
Jan 06 13:11:51 hai0620 systemd-sleep[16438]: storing slimbook configuration:0
Jan 06 13:11:51 hai0620 systemd-sleep[16434]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for bootloader: grub2-bls
Jan 06 13:11:51 hai0620 systemd-sleep[16421]: Performing sleep operation 'hibernate'...
Jan 06 13:11:51 hai0620 kernel: PM: hibernation: hibernation entry
Jan 06 13:11:52 hai0620 kernel: Filesystems sync: 0.008 seconds
-- Boot 247c6e7ec5f1449d9ef7f70cd1055b70 --
Jan 06 13:14:42 hai0620 kernel: Linux version 6.18.2-1-default (geeko@buildhost) (gcc (SUSE Linux) 15.2.1 20251006, GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.45.0.20251103-2) #1 SMP PREEMPT_DYNAMIC Fri Dec 19 10:15:01 UTC 2025 (9447271)
Jan 06 13:14:42 hai0620 kernel: Command line: BOOT_IMAGE=(hd0,gpt1)/opensuse-tumbleweed/6.18.2-1-default/linux-17aa742ebbe34d76bee9df1adf8e7f49d838c330 splash=silent resume=/dev/suse/swap mitigations=auto security=selinux selinux=1 acpi.ec_n>

Good afternoon, Markku

Please contact with our support team at https://slimbook.com/support

Regards,

Hi, I have done that now, gracias!

I'm also experiencing the same issue with my Evo 14 with the AI9 365 CPU. I'm just running the Slimbook OS 24 that the laptop came with, and it doesn't resume from both sleep or hibernate. I also confirmed that I have the meta packages installed, and my grub entry has the following flags

quiet splash amd_iommu=off acpi.ec_no_wakeup=1 fbcon=nodefer plymouth.use-simpledrm amdgpu.dcdebugmask=0x610

-- Boot f801429ad6a54034beebe3ed281e640f --
Jan 05 15:23:01 asrv-slimbook-kde systemd-sleep[5370]: storing slimbook configuration:0
Jan 05 15:23:01 asrv-slimbook-kde systemd-sleep[5351]: Performing sleep operation 'suspend'...
Jan 05 15:23:07 asrv-slimbook-kde systemd-sleep[5351]: System returned from sleep operation 'suspend'.
Jan 05 15:23:07 asrv-slimbook-kde systemd-sleep[5509]: loading slimbook configuration:0
Jan 05 17:10:08 asrv-slimbook-kde systemd-sleep[67759]: storing slimbook configuration:0
Jan 05 17:10:08 asrv-slimbook-kde systemd-sleep[67741]: Performing sleep operation 'suspend'...
-- Boot 9765aaa91d684b549851bfddcc52656e --
Jan 06 19:28:28 asrv-slimbook-kde systemd-sleep[289442]: storing slimbook configuration:0
Jan 06 19:28:28 asrv-slimbook-kde systemd-sleep[289436]: Performing sleep operation 'hibernate'...
Jan 06 19:29:03 asrv-slimbook-kde systemd-sleep[289436]: System returned from sleep operation 'hibernate'.
Jan 06 19:29:03 asrv-slimbook-kde systemd-sleep[289694]: loading slimbook configuration:0
Jan 06 21:29:04 asrv-slimbook-kde systemd-sleep[351957]: storing slimbook configuration:0
Jan 06 21:29:04 asrv-slimbook-kde systemd-sleep[351951]: Performing sleep operation 'hibernate'...
Jan 06 21:29:31 asrv-slimbook-kde systemd-sleep[351951]: System returned from sleep operation 'hibernate'.
Jan 06 21:29:31 asrv-slimbook-kde systemd-sleep[352229]: /usr/lib/systemd/system-sleep/slimbook-i8042-reset: 7: echo: echo: I/O error
Jan 06 21:29:31 asrv-slimbook-kde systemd-sleep[352233]: loading slimbook configuration:0
Jan 06 23:29:33 asrv-slimbook-kde systemd-sleep[414470]: storing slimbook configuration:0
Jan 06 23:29:33 asrv-slimbook-kde systemd-sleep[414464]: Performing sleep operation 'hibernate'...
Jan 06 23:30:00 asrv-slimbook-kde systemd-sleep[414464]: System returned from sleep operation 'hibernate'.
Jan 06 23:30:00 asrv-slimbook-kde systemd-sleep[414755]: /usr/lib/systemd/system-sleep/slimbook-i8042-reset: 7: echo: echo: I/O error
Jan 06 23:30:00 asrv-slimbook-kde systemd-sleep[414759]: loading slimbook configuration:0
Jan 07 01:30:01 asrv-slimbook-kde systemd-sleep[476977]: storing slimbook configuration:0
Jan 07 01:30:01 asrv-slimbook-kde systemd-sleep[476971]: Performing sleep operation 'hibernate'...
Jan 07 01:30:28 asrv-slimbook-kde systemd-sleep[476971]: System returned from sleep operation 'hibernate'.
Jan 07 01:30:28 asrv-slimbook-kde systemd-sleep[477287]: /usr/lib/systemd/system-sleep/slimbook-i8042-reset: 7: echo: echo: I/O error
Jan 07 01:30:28 asrv-slimbook-kde systemd-sleep[477291]: loading slimbook configuration:0
Jan 07 03:30:29 asrv-slimbook-kde systemd-sleep[539374]: storing slimbook configuration:0
Jan 07 03:30:29 asrv-slimbook-kde systemd-sleep[539368]: Performing sleep operation 'hibernate'...
Jan 07 03:30:56 asrv-slimbook-kde systemd-sleep[539368]: System returned from sleep operation 'hibernate'.
Jan 07 03:30:56 asrv-slimbook-kde systemd-sleep[539763]: /usr/lib/systemd/system-sleep/slimbook-i8042-reset: 7: echo: echo: I/O error
Jan 07 03:30:56 asrv-slimbook-kde systemd-sleep[539767]: loading slimbook configuration:0
Jan 07 05:30:57 asrv-slimbook-kde systemd-sleep[602057]: storing slimbook configuration:0
Jan 07 05:30:57 asrv-slimbook-kde systemd-sleep[602051]: Performing sleep operation 'hibernate'...
Jan 07 05:31:25 asrv-slimbook-kde systemd-sleep[602051]: System returned from sleep operation 'hibernate'.
Jan 07 05:31:25 asrv-slimbook-kde systemd-sleep[602367]: /usr/lib/systemd/system-sleep/slimbook-i8042-reset: 7: echo: echo: I/O error
Jan 07 05:31:25 asrv-slimbook-kde systemd-sleep[602371]: loading slimbook configuration:0
-- Boot 8e05c126fd4f4c1c8d853849e422a637 --
Jan 07 10:44:08 asrv-slimbook-kde systemd-sleep[7196]: storing slimbook configuration:0
Jan 07 10:44:08 asrv-slimbook-kde systemd-sleep[7177]: Performing sleep operation 'suspend'...
Jan 07 10:44:39 asrv-slimbook-kde systemd-sleep[7177]: System returned from sleep operation 'suspend'.
Jan 07 10:44:39 asrv-slimbook-kde systemd-sleep[7352]: loading slimbook configuration:0
Jan 07 16:36:56 asrv-slimbook-kde systemd-sleep[18257]: storing slimbook configuration:0

@asrv I will post here when/if I get suspension working, but I think it's worth opening a support ticket.

Good morning @asrv

You could try switching kernels and check if the issue mitigates, with SlimbookOS 24, it comes with `linux-oem-24.04d` which should put you with Kernel 6.17, if you are on 6.17 you can try lowering the kernel to 6.14 which is the kernel we are using by default (eg, see this, it is another case of not being able to suspend and changing Kernels fixed it)

However, if the device doesn't come back from suspend with the same blinking LED problem, it might be better to open a support ticket, as our support team will help you with your issue 


Regards,

Hi,

I confirm I have the same problem here with a slimbook EVO 14 AMD Ryzen AI9 365 I bought in December, which came with BIOS "N.1.20GOS03" (EC "1.24").

I see the same symptoms: suspending the laptop (closing the lid or running "systemctl suspend" ) powers off the screen and leaves the led blinking. From there, trying to resume by pressing the power button doesn't work, it does nothing. Only thing I can do is long-pressing the button to power off.

IIRC I did some tests a few days ago by changing the maximum sleep power state through kernel cmdline param "processor.max_cstate=1" and then I could suspend+resume correctly but only once, suspending again would fail to resume until I power off the laptop.

I'm running Archlinux with kernel 6.18.2-arch2-1, so FYI this is not yet fixed in newer kernels.

It would be great to have this solved soon, since it's the only big issue with the laptop I found so far, but makes it unsuitable for traveling, where suspending is required.

I just upgraded to kernel 6.18.4-arch1-1 and still getting same faulty behavior.

It smells it could be BIOS/firmware/ACPI related? Whenever I power off the laptop due to failing resume from suspend, next time I power on I can hear the fans and the led turning on, but the screen doesn't power on. I need to power it off again and then on next power on it just works. This happens consistently a few times I tried in the past AFAIR, and it happened just now when I tried with the new kernel version.

Good morning, pespin
If the blinking LED problem after suspending and trying to wake up exists, it should be better to contact with our support team at https://slimbook.com/support

Regardless anything, do note that this laptop needs specific packages/kernel parameters to function properly, you can see the kernel parameters here 
Assuming you do not use GRUB with your Archlinux installation, you need to put the kernel parameters yourself, otherwise, just installing the packages should be enough (though you should still contact support, as they will help you)

Regards,

Hi, and just to add, when booting verify the kernel parameters are set. I noticed that my Opensuse didn't have those parameters set although I had installed the slimbook packages. It turned out, that OpenSUSE recently moved to grub2-bls on new installs (see announcement https://news.opensuse.org/2025/11/13/tw-grub2-bls/ ), I had to set the kernel parameters in /etc/kernel/cmdline , not in  /etc/default/grub .

> Hi, and just to add, when booting verify the kernel parameters are set

Ack, I'm doing that by checking "slash proc slash cmdline" (writing it this way because yesterday I was blocked for this...).

I updated Archlinux and now I have kernel 6.18.5-arch1-1. I also installed the slimbook Arch repo from https://download.opensuse.org/repositories/home:/Slimbook/Arch/x86_64/ , and installed the packages: slimbook-quirk-i8042-wakeup slimbook-grub-fix-ecwake slimbook-quirk-i8042-reset slimbook-yt6801-dkms slimbook-qc71-dkms

Regarding slimbook-grub-fix-psr, it actually doesn't exist in the Arch repo (probably something Slimbook support needs to fix), but I added fbcon=nodefer manually to grub.

Then I rebooted, and I'm still getting the problem with resume from suspend not working and the power led that keeps blinking.

Good morning, pespin
The PKGBUILD that we use for our Arch repos has the PSR package defined, and also has a package built within Open Build System

>Regarding slimbook-grub-fix-psr, it actually doesn't exist in the Arch repo (probably something Slimbook support needs to fix), but I >added fbcon=nodefer manually to grub.

slimbook-grub-fix-psr adds amdgpu.dcdebugmask=0x610 to GRUB, not fbcon=nodefer
It is true that the fbcon=nodefer package is not included in our Arch repos, we will fix that ASAP

In any case, if adding amdgpu's dcdebugmask doesn't fix your issue, then contact the support team at https://slimbook.com/support

Regards,

I contacted support and got my issue fixed.

Hi Markku,

I opened a support ticket but got no answer yet. Do you mind sharing the steps you used to fix the issue with resume/suspend?

For reference: The laptop came with a pair of RAM modules from a defective batch which generates the suspend issues.

Support provided me with a new pair of RAM modules and the "no resume from suspend" issue is solved now.