No wake up from sleep after upgrading to Zen Kernel 6.19.8

[DenalB]

Some hours ago I got the latest Zen Kernel 6.19.8 installed. Since then my system is not waking up from sleep anymore. Until Zen Kernel 6.19.6 was used, there were no issues. I have tried twice since I upgraded.

On the first try, my system woke up, but it didn’t recognize any key. My monitor was still in sleep mode. On the second try my system and monitor woke up. The mouse cursor was there already, and I could move it. But nothing happened.

I had to power off my system. After turning it on again, everything looked good so far.

Is anyone else having this problem?

Maybe I have to say that I’m actually on Arch Linux.

System:
  Kernel: 6.19.8-zen1-1-zen arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.6.2 Distro: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG X570 TOMAHAWK WIFI (MS-7C84)
    v: 1.0 serial: <superuser required> Firmware: UEFI vendor: American
    Megatrends LLC. v: 1.K1 date: 09/10/2025
CPU:
  Info: 12-core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP cache:
    L2: 6 MiB
  Speed (MHz): avg: 3600 min/max: 563/4674 cores: 1: 3600 2: 3600 3: 3600
    4: 3600 5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600
    13: 3600 14: 3600 15: 3600 16: 3600 17: 3600 18: 3600 19: 3600 20: 3600
    21: 3600 22: 3600 23: 3600 24: 3600
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [Radeon RX 9070/9070
    XT/9070 GRE] driver: amdgpu v: kernel
  Device-2: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
    type: USB
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu
    resolution: 3440x1440~144Hz
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 26.0.2-arch1.1
    renderer: AMD Radeon RX 9070 XT (radeonsi gfx1201 ACO DRM 3.64
    6.19.8-zen1-1-zen)
  API: Vulkan v: 1.4.341 drivers: radv surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
    Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 48 HDMI/DP Audio
    driver: snd_hda_intel
  Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
    type: USB
  API: ALSA v: k6.19.8-zen1-1-zen status: kernel-api
  Server-1: PipeWire v: 1.6.1 status: active
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169
  IF: enp38s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb type: USB
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Drives:
  Local Storage: total: 7.28 TiB used: 3.17 TiB (43.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
    size: 1.82 TiB
  ID-3: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
  ID-4: /dev/sdb vendor: Western Digital model: WD20EZBX-00AYRA0
    size: 1.82 TiB
  ID-5: /dev/sdc vendor: Western Digital model: WD20EZBX-00AYRA0
    size: 1.82 TiB
Partition:
  ID-1: / size: 930.51 GiB used: 48.73 GiB (5.2%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-2: /boot size: 1022 MiB used: 126.9 MiB (12.4%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 930.51 GiB used: 48.73 GiB (5.2%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-4: /var/log size: 930.51 GiB used: 48.73 GiB (5.2%) fs: btrfs
    dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: zram size: 15.63 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 38.2 C mobo: N/A gpu: amdgpu temp: 33.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 4
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 3.53 GiB (11.3%)
  Processes: 564 Uptime: 13m Shell: Bash inxi: 3.3.40

[eso]

journalctl -b 0 | grep -e 'suspend' -e 'resume'
márc 16 00:06:51 a-83k7 kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=8ab204af-ea07-447a-813d
-bfa055df251d rw rootflags=subvol=@ resume=UUID=3b9ef009-065a-422e-8599-ee654bd3fadf nowatchdog nvme_load=YES loglev
el=3 i8042.reset i8042.nomux=1
márc 16 00:06:51 a-83k7 kernel: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=8ab204af-ea07-44
7a-813d-bfa055df251d rw rootflags=subvol=@ resume=UUID=3b9ef009-065a-422e-8599-ee654bd3fadf nowatchdog nvme_load=YES
loglevel=3 i8042.reset i8042.nomux=1
márc 16 00:06:51 a-83k7 kernel: Low-power S0 idle used by default for system suspend
márc 16 00:06:52 a-83k7 dracut-cmdline[257]: Using kernel command line parameters: BOOT_IMAGE=/@/boot/vmlinuz-lin
ux-zen root=UUID=8ab204af-ea07-447a-813d-bfa055df251d rw rootflags=subvol=@ resume=UUID=3b9ef009-065a-422e-8599-ee65
4bd3fadf nowatchdog nvme_load=YES loglevel=3 i8042.reset i8042.nomux=1
márc 16 00:06:52 a-83k7 kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
márc 16 00:06:52 a-83k7 systemd-hibernate-resume[415]: Unable to resume from device '/dev/disk/by-uuid/3b9ef009-065a
-422e-8599-ee654bd3fadf' (259:3) offset 0, continuing boot process.
márc 16 00:06:52 a-83k7 systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
márc 16 00:07:01 a-83k7 rtkit-daemon[1201]: Handling system-suspend using logind.
márc 16 00:07:47 a-83k7 systemd-logind[881]: The system will suspend now!
márc 16 00:07:48 a-83k7 systemd-sleep[2706]: Performing sleep operation 'suspend'...
márc 16 00:07:48 a-83k7 kernel: PM: suspend entry (s2idle)
márc 16 00:07:56 a-83k7 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
márc 16 00:07:56 a-83k7 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
márc 16 00:07:57 a-83k7 systemd-sleep[2706]: System returned from sleep operation 'suspend'.
márc 16 00:07:57 a-83k7 kernel: PM: suspend exit
márc 16 00:07:57 a-83k7 systemd[1]: systemd-suspend.service: Deactivated successfully.
márc 16 00:07:57 a-83k7 systemd-logind[881]: Operation 'suspend' finished.

It works here with 6.19.8-zen1-1-zen

[DenalB]

Tried again now, and this time it worked…

$ journalctl -b 0 | grep -e 'suspend' -e 'resume'
Mar 16 10:45:01 PROMETHEUS-ArchLinux rtkit-daemon[1045]: Handling system-suspend using logind.
Mar 16 11:01:41 PROMETHEUS-ArchLinux systemd-logind[817]: The system will suspend now!
Mar 16 11:01:42 PROMETHEUS-ArchLinux systemd-sleep[13699]: Performing sleep operation 'suspend'...
Mar 16 11:01:42 PROMETHEUS-ArchLinux kernel: PM: suspend entry (deep)
Mar 16 11:02:04 PROMETHEUS-ArchLinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 16 11:02:04 PROMETHEUS-ArchLinux kernel: ACPI: PM: Low-level resume complete
Mar 16 11:02:04 PROMETHEUS-ArchLinux systemd-sleep[13699]: System returned from sleep operation 'suspend'.
Mar 16 11:02:04 PROMETHEUS-ArchLinux kernel: amdgpu 0000:2f:00.0: amdgpu: SMU is resumed successfully!
Mar 16 11:02:04 PROMETHEUS-ArchLinux systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 16 11:02:04 PROMETHEUS-ArchLinux systemd-logind[817]: Operation 'suspend' finished.
Mar 16 11:02:04 PROMETHEUS-ArchLinux kernel: PM: suspend exit

Was it perhaps a coincidence? I’ll keep an eye on this …

[DenalB]

I just want to let you all know that there were no issues again. Sleep mode works without issues. Looks like it was a coincidence … Fingers crossed.

[DenalB]

I shouldn’t have written anything. Right after writing my answer yesterday, there was the next issue with Zen Kernel 6.19.8.

And after upgrading to Zen Kernel 6.19.9 today, I got the next crash when trying to wake up my system from sleep mode.

[eso]

IDK AMD Ryzen 5 7533HS 16G RAM. I saw a Kernal Panic screen today but not with zen kernel.
I think external SSD caused it.

[DenalB]

Some minutes ago I was able to wake up my system from sleep mode without issues. Strange…

[DenalB]

Could it be that this is my issue, too?

@BishopWolf

I’m not sure if this has been said. But plasma login manager does not respond after waking up from sleep if you have kde wallet active at the moment. Theoretically you shall unlock it with a dialog, but first you have to login. You can’t login because you can’t unlock the wallet.

The solution is restart the machine and disable kde wallet, or , don’t call the login manager after sleep.

I have to try disabling KDE Wallet. Hopefully it solves my issue.