Suspend and resume issues amd gpu/cpu

I’m attempting to resolve sleep issues on KDE Plasma. I’ve experimented with s2idle and deep; however, my fans become excessively loud on s2idle, and my display fails to recover from a black screen. My entire system freezes upon suspension, and only the display resumes when using deep. I have journal logs from two different boots. The problem occurs inconsistently; sometimes resuming is possible, other times it’s not. I’m using the default kernel from the ISO, and my system is updated, featuring an AMD R9 7950X and an AMD RX 7900 XTX. Any assistance would be greatly appreciated.

able to suspend log

not able to suspend log

I’ve got the same problem, I thought it was a setting in my BIOS but turns out I encounter this on several different laptops that I’ve installed CachyOS on with KDE.

1 Like

I am having similar issues. Sometimes it comes back from suspend, other times I have to hard reset.

The same here. After resuming X11 screen flashes and goes dark. For now I´m using the arch kernel on my laptop.

Are you saying that Arch kernel works fine but not CachyOS kernel? If yes, please let me known your system specs, and also if you’re using mediatek or not. Thanks.

BlockquoteSystem:
Host: pulse2 Kernel: 6.12.4-arch1-1 arch: x86_64 bits: 64 compiler: gcc
v: 14.2.1
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A wm: kwin_x11 dm: SDDM
Distro: CachyOS base: Arch Linux
Machine:
Type: Laptop System: TUXEDO product: TUXEDO Pulse 15 Gen2 v: Standard
serial:
Mobo: NB02 model: PF5LUXG v: Standard serial:
part-nu: PULSE1502 uuid: UEFI: American Megatrends LLC.
v: N.1.06A13 date: 06/21/2023
Battery:
ID-1: BAT0 charge: 60.1 Wh (96.0%) condition: 62.6/91.6 Wh (68.4%)
volts: 11.7 min: 11.6 model: standard serial: 00001 status: discharging
Memory:
System RAM: total: 64 GiB available: 60.71 GiB used: 6.42 GiB (10.6%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 64 GiB note: est. slots: 2 modules: 2 EC: None
max-module-size: 32 GiB note: est.
Device-1: Channel-A DIMM 0 type: DDR4 size: 32 GiB speed: 3200 MT/s
volts: 1 note: check manufacturer: Samsung part-no: M471A4G43AB1-CWE
Device-2: Channel-B DIMM 0 type: DDR4 size: 32 GiB speed: 3200 MT/s
volts: 1 note: check manufacturer: Samsung part-no: M471A4G43AB1-CWE
CPU:
Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 8 MiB
Speed (MHz): avg: 1560 min/max: 400/4372 boost: enabled cores: 1: 1560
2: 1560 3: 1560 4: 1560 5: 1560 6: 1560 7: 1560 8: 1560 9: 1560 10: 1560
11: 1560 12: 1560 13: 1560 14: 1560 15: 1560 16: 1560 bogomips: 57505
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Lucienne vendor: AIstone Global
driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports:
active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 05:00.0 chip-ID: 1002:164c
temp: 30.0 C
Device-2: Chicony Integrated IR Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 04f2:b71a
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 144
Monitor-1: eDP-1 model: BOE Display 0x0974 res: 2560x1440 dpi: 189
diag: 395mm (15.5")
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.2-cachyos1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
renoir LLVM 18.1.8 DRM 3.59 6.12.4-arch1-1) device-ID: 1002:164c
API: Vulkan v: 1.4.303 surfaces: xcb,xlib device: 0 type: integrated-gpu
driver: N/A device-ID: 1002:164c
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
Audio vendor: AIstone Global driver: snd_hda_intel v: kernel pcie:
speed: 8 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1637
Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
vendor: AIstone Global driver: N/A pcie: speed: 8 GT/s lanes: 16
bus-ID: 05:00.5 chip-ID: 1022:15e2
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: AIstone Global driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3
API: ALSA v: k6.12.4-arch1-1 status: kernel-api
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: AIstone Global driver: r8169 v: kernel pcie: speed: Unknown
lanes: 63 port: f000 bus-ID: 01:00.0 chip-ID: 10ec:8168
IF: enp1s0 state: down mac: b0:25:aa:4e:d5:04
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723
IF: wlan0 state: up mac: 14:85:7f:0c:5d:6e
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-4.4:4 chip-ID: 8087:0029
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: 14:85:7F:0C:5D:72
bt-v: 5.2 lmp-v: 11
Drives:
Local Storage: total: 7.28 TiB used: 487.65 GiB (6.5%)
ID-1: /dev/nvme0n1 vendor: Seagate model: FireCuda 530 ZP4000GM30013
size: 3.64 TiB speed: 63.2 Gb/s lanes: 4 serial: 7VS00L8M temp: 13.8 C
ID-2: /dev/nvme1n1 vendor: Seagate model: FireCuda 530 ZP4000GM30013
size: 3.64 TiB speed: 63.2 Gb/s lanes: 4 serial: 7VS00LTN temp: 12.8 C
Partition:
ID-1: / size: 3.64 TiB used: 487.64 GiB (13.1%) fs: btrfs dev: /dev/dm-0
mapped: luks-55c36ee0-3aca-42f4-828c-d438f9f0e109 label: N/A
uuid: b2dfaa29-cc8e-4574-909c-d63b22f1932e
ID-2: /boot/efi size: 299.4 MiB used: 4.1 MiB (1.4%) fs: vfat
dev: /dev/nvme0n1p1 label: N/A uuid: EFB8-027C
ID-3: /home size: 3.64 TiB used: 487.64 GiB (13.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-55c36ee0-3aca-42f4-828c-d438f9f0e109 label: N/A
uuid: b2dfaa29-cc8e-4574-909c-d63b22f1932e
ID-4: /root size: 3.64 TiB used: 487.64 GiB (13.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-55c36ee0-3aca-42f4-828c-d438f9f0e109 label: N/A
uuid: b2dfaa29-cc8e-4574-909c-d63b22f1932e
ID-5: /srv size: 3.64 TiB used: 487.64 GiB (13.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-55c36ee0-3aca-42f4-828c-d438f9f0e109 label: N/A
uuid: b2dfaa29-cc8e-4574-909c-d63b22f1932e
ID-6: /var/cache size: 3.64 TiB used: 487.64 GiB (13.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-55c36ee0-3aca-42f4-828c-d438f9f0e109 label: N/A
uuid: b2dfaa29-cc8e-4574-909c-d63b22f1932e
ID-7: /var/log size: 3.64 TiB used: 487.64 GiB (13.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-55c36ee0-3aca-42f4-828c-d438f9f0e109 label: N/A
uuid: b2dfaa29-cc8e-4574-909c-d63b22f1932e
ID-8: /var/tmp size: 3.64 TiB used: 487.64 GiB (13.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-55c36ee0-3aca-42f4-828c-d438f9f0e109 label: N/A
uuid: b2dfaa29-cc8e-4574-909c-d63b22f1932e
Swap:
ID-1: swap-1 type: zram size: 60.71 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 33.0 C mobo: N/A gpu: amdgpu temp: 31.0 C
Fan Speeds (rpm): N/A

I believe the only thing we do differently with respect to suspend and resume is a patchset that aims to fix suspending when system memory is fragmented. Can you try our rc kernel and check if that’s problematic too? That kernel doesn’t have the suspend fix yet.

sudo pacman -S linux-cachyos-rc linux-cachyos-rc-headers

on rc-kernel it works without probs.

Surely it’s that suspend fix then. I will build a test kernel for you with a revert.

thank you…using cachy about 2 years but did not know that here are nice guys.

It’s almost done building. In the meantime, could you try to suspend with the broken kernel and grab some logs. If you can’t access the machine on resume, you can boot into a new session and grab the log from a previous session with the following command

journalctl -b -1 | paste-cachyos

-1 is the first last boot relative to the current boot session.

Nginx Directory Here it is.

sadly it is not working…have to setup ssh first for debugging

Hmmmm, did this happen on older kernels? such as 6.12.5 or 6.12.4

If you haven’t tried, please install an older kernel.

sudo pacman -U https://archive.cachyos.org/archive/cachyos-v3/linux-cachyos-6.12.5-2-x86_64_v3.pkg.tar.zst https://archive.cachyos.org/archive/cachyos-v3/linux-cachyos-headers-6.12.5-2-x86_64_v3.pkg.tar.zst

This is the command for 6.12.5

I think it began 6.12.4. On resume the screen flashes once twice…and everytime faster until it is dark. Sometimes I can switch tty and restart sddm.

There are varying kernel versions in CachyOS - Repo. Please try each version and let me know which kernel is the last working version and which is the first to break for you. Thanks

Examples:

  • linux-cachyos - 6.12.3, 6.12.4, 6.12.5
  • linux-cachyos-bmq - 6.12.2
  • linux-cachyos-deckify - 6.12.1
  • linux-cachyos-autofdo - 6.12.0

Ok Linux 6.12.3-1-cachyos works. I keep this one now.

There weren’t any changes between 6.12.3 to 6.12.4 as far as I can see. I would say it’s an upstream issue if it weren’t for the fact that Arch’s kernel is working. They’re still on 6.12.4 while we’re on 6.12.6 so it might still be plausible.

Ok thanks. I will test every following kernels.

and another laptop with the same issue…holding 6.12.3 also for now