Bug 511597

SUMMARY
When suspending the system via keyboard shortcut, the system never fully suspends and immediately wakes ~5 seconds later with no action taken. If machine is suspended via sudo systemctl suspend, the machine successfully enters suspend mode and does not immediately wake up.


STEPS TO REPRODUCE
1. Set "Suspend" to a keyboard shortcut (eg. Meta+Shift+L)
2. Suspend system via shortcut
3. Wait ~5 seconds

OBSERVED RESULT
Machine never fully suspends (fans do not stop, screens never fully power off, etc) before waking back up. Notably bluetooth ceases to function after a failed suspend (controller missing).

EXPECTED RESULT
Machine properly enters suspend and fans stop spinning etc.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.6-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 4070
Graphics Processor 2: AMD Ryzen 7 9800X3D 8-Core Processor


ADDITIONAL INFORMATION

I think this has something to do with the onboard gpu on my Ryzen 7 9800X3D cpu. If I disable it via motherboard north bridge settings, the suspend keyboard shortcut immediately starts working except that the system no longer wakes cleanly. Another oddity is that bluetooth ends up in a broken state when it doesn't fully suspend. Service is running but it no longer sees the bluetooth controller (ie. bluetoothctl reports no controllers) even though it's there and everything is working on a clean boot.

Relevant lines from dmesg after a bad suspend:
[   85.828778] PM: suspend entry (s2idle)
[   85.845043] Filesystems sync: 0.016 seconds
[   85.845467] Freezing user space processes
[   85.846564] Freezing user space processes completed (elapsed 0.001 seconds)
[   85.846567] OOM killer disabled.
[   85.846567] Freezing remaining freezable tasks
[   85.865945] Bluetooth: hci0: HW/SW Version: 0x00000000, Build Time: 20250825220109
[   85.966248] Freezing remaining freezable tasks completed (elapsed 0.119 seconds)
[   85.966250] printk: Suspending console(s) (use no_console_suspend to debug)
[   85.966367] amdgpu 0000:73:00.0: amdgpu: Power consumption will be higher as BIOS has not been configured for suspend-to-idle
.
               To use suspend-to-idle change the sleep mode in BIOS setup.
[   85.966965] amdgpu 0000:73:00.0: amdgpu: [drm] *ERROR* Unsupported suspend state 1
[   85.966968] amdgpu 0000:73:00.0: PM: pci_pm_suspend(): amdgpu_pmops_suspend [amdgpu] returns -22
[   85.967099] amdgpu 0000:73:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -22
[   85.967107] amdgpu 0000:73:00.0: PM: failed to suspend async: error -22
[   85.967350] serial 00:04: disabled
[   85.977784] queueing ieee80211 work while going to suspend
[   85.983627] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   86.090535] PM: Some devices failed to suspend, or early wake event detected
[   86.093131] serial 00:04: activated
[   86.252869] PM: resume devices took 0.162 seconds
[   86.253010] OOM killer enabled.
[   86.253010] Restarting tasks: Starting
[   86.253617] Restarting tasks: Done
[   86.253702] random: crng reseeded on system resumption
[   86.253706] PM: suspend exit


Relevant lines from dmesg after running systemctl suspend:
[  109.189840] PM: suspend entry (deep)
[  109.581821] Filesystems sync: 0.391 seconds
[  109.616632] Freezing user space processes
[  109.617696] Freezing user space processes completed (elapsed 0.001 seconds)
[  109.617698] OOM killer disabled.
[  109.617699] Freezing remaining freezable tasks
[  109.618686] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[  109.618714] printk: Suspending console(s) (use no_console_suspend to debug)
[  109.620161] serial 00:04: disabled
[  109.626677] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  109.629471] ata1.00: Entering standby power mode
[  110.143202] PM: suspend devices took 0.524 seconds