Hey Fedora friends,
I have a problem, that occurred already some time ago with a kernel update in Fedora 38 and still persists in Fedora 39 - as described in the headline my system can suspend just one time. First time everything is totally fine, but if I try another suspend the screen is black for one second and I end up directly on the lockscreen.
So I was looking a bit deeper into journalctl (but I’m not that professional) and found some error messages:
Jan 02 12:31:21 localhost.localdomain systemd-logind[2112]: The system will suspend now!
Jan 02 12:31:21 localhost.localdomain ModemManager[2086]: <info> [sleep-monitor-systemd] system is about to suspend
Jan 02 12:31:22 localhost.localdomain systemd[1]: Starting systemd-suspend.service - System Suspend...
Jan 02 12:31:23 localhost.localdomain systemd-sleep[5029]: Entering sleep state 'suspend'...
Jan 02 12:31:23 localhost.localdomain kernel: PM: suspend entry (deep)
Jan 02 12:31:23 localhost.localdomain kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 02 12:31:23 localhost.localdomain kernel: nvme 0000:01:00.0: PM: pci_pm_suspend(): nvme_suspend+0x0/0x170 [nvme] returns -16
Jan 02 12:31:23 localhost.localdomain kernel: nvme 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
Jan 02 12:31:23 localhost.localdomain kernel: nvme 0000:01:00.0: PM: failed to suspend async: error -16
Jan 02 12:31:23 localhost.localdomain kernel: PM: Some devices failed to suspend, or early wake event detected
Jan 02 12:31:24 localhost.localdomain kernel: PM: suspend exit
Jan 02 12:31:24 localhost.localdomain kernel: PM: suspend entry (s2idle)
Jan 02 12:31:25 localhost.localdomain kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 02 12:31:25 localhost.localdomain kernel: nvme 0000:01:00.0: PM: pci_pm_suspend(): nvme_suspend+0x0/0x170 [nvme] returns -16
Jan 02 12:31:25 localhost.localdomain kernel: nvme 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
Jan 02 12:31:25 localhost.localdomain kernel: nvme 0000:01:00.0: PM: failed to suspend async: error -16
Jan 02 12:31:25 localhost.localdomain kernel: PM: Some devices failed to suspend, or early wake event detected
Jan 02 12:31:25 localhost.localdomain kernel: PM: suspend exit
Jan 02 12:31:25 localhost.localdomain systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
Jan 02 12:31:25 localhost.localdomain systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
Jan 02 12:31:25 localhost.localdomain systemd[1]: Failed to start systemd-suspend.service - System Suspend.
Jan 02 12:31:25 localhost.localdomain systemd[1]: Dependency failed for suspend.target - Suspend.
Jan 02 12:31:25 localhost.localdomain systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Jan 02 12:31:25 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
My system (HP ProBook 650 G5) has a NVME SSD with bitlocker encrypted Windows 10 and my Fedora installation running on a SATA SSD. If I understand the error correctly, the nvme SSD seems to be the culprit, but I could not find any useful informations on the web about this problem.
Thanks in advance.