PC won't wake from Suspend?

Issues & Assistance
1

Hello, I’ve been using cachyos for a while and during the entire time I’ve used it when my PC goes into suspend I can’t get it to wake from simple mouse/keyboard input. I have to flip the switch on my PSU off and on for it to wake. I’ve tried fixing it before but I didn’t have any luck and decided to ask the forum here. I’m on Gnome 48, wayland, cachyos-lts kernal, all AMD system. Waking from windows is no problem, and on my laptop (with CachyOS) it also works so I imagine there’s something I can do.

I found these in my logs, so I think the usb devices are failing to wake?
kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit

kernel: usb usb1: root hub lost power or was reset

kernel: usb usb2: root hub lost power or was reset

I tried adding these to grub config but no luck:
usbcore.autosuspend=-1

iommu=soft

acpi_osi='!Windows 2012'

fastfetch:

nick@NickLinux

OS: CachyOS x86_64
Host: B550 AORUS ELITE V2
Kernel: Linux 6.12.47-2-cachyos-lts
Uptime: 6 days, 45 mins
Packages: 2086 (pacman), 106 (flatpak-system), 17 (flatpak-user), 6 (snap)
Shell: fish 4.0.6
Display (MG248): 1920x1080 in 24", 144 Hz [External]
Display (H27T22): 2560x1440 in 27", 170 Hz [External] *
DE: GNOME 48.4
WM: Mutter (Wayland)
WM Theme: Adwaita-dark
Theme: Adwaita-dark [GTK2/3/4]
Icons: Colloid-Dark [GTK2/3/4]
Font: Product Sans (10pt) [GTK2/3/4]
Cursor: Colloid (24px)
Terminal: gjs
CPU: AMD Ryzen 7 5800X3D (16) @ 4.55 GHz
GPU: AMD Radeon RX 7800 XT [Discrete]
Memory: 12.87 GiB / 46.95 GiB (27%)
Swap: 3.21 GiB / 46.95 GiB (7%)
Disk (/): 1.10 TiB / 1.82 TiB (61%) - btrfs
Disk (/mnt/069268B99268AEBD): 314.65 GiB / 462.26 GiB (68%) - fuseblk
Disk (/mnt/HDD-Linux): 1.31 TiB / 3.58 TiB (37%) - ext4
Local IP (eno1): 192.168.4.33/22
Locale: en_US.UTF-8

2

Hi, it’s a known bug with amd, there are plenty of threads with sleep and wake up problems. It seems to be related to incomplete acpi tables for S3.

I am facing a similar problem too, and opened a issue on bugzilla. Mario Limonciello (many thanks to him !) from AMD ingeeners team helped me, and asked me to install the release candidate 6.17 kernel. I do not try yet but you should give a try.

Here is the bugzilla topic:

3

Thanks for the info, that actually makes a lot of sense considering the issue happens across multiple distros and DEs.

I’ll try the 6.17 RC kernel and see if it improves anything. Thanks for sharing the Bugzilla thread.