Unable to reboot/shutdown after suspend in Fedora 40

Hello everyone,

After upgrading to Fedora 40, I am unable to reboot or shutdown my machine. I get stuck on a black screen that shows nothing and I have to shutdown using the physical power button. This only happens when I reboot/shutdown after having suspended once during my session, otherwise the reboot works.

This is what I get from journalctl

journalctl -b -1 -r -p err
Apr 30 13:08:29 fedora kernel: watchdog: watchdog0: watchdog did not stop!
Apr 30 13:08:28 fedora dbus-broker-launch[970]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 30 13:08:28 fedora dbus-broker-launch[970]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 30 13:08:28 fedora dbus-broker-launch[970]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 30 13:08:28 fedora dbus-broker-launch[970]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 30 13:08:13 fedora kernel: usb 7-1.5: PM: failed to resume async: error -5
Apr 30 13:08:13 fedora kernel: usb 7-1.5: PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
Apr 30 13:08:13 fedora kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 30 13:08:13 fedora kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 30 13:08:05 fedora bluetoothd[973]: src/gatt-database.c:client_ready_cb() Failed to create GATT service entry in local database
Apr 30 13:08:05 fedora bluetoothd[973]: src/gatt-database.c:database_add_app() Failed to add service
Apr 30 13:08:05 fedora bluetoothd[973]: src/gatt-database.c:database_add_service() Failed to add characteristic
Apr 30 13:08:05 fedora bluetoothd[973]: src/gatt-database.c:database_add_chrc() Failed to create characteristic entry in database

Try adding reboot=pci as a kernel option, reboot, suspend, and try reboot again. If that doesn’t fix anything, try reboot=efi.

If one of those work, I’m assuming a kernel update changed something with how reboot works on your motherboard and it isn’t ideal. One of those values might cause rebooting to take a different method, and on my laptop using pci causes it to reboot hard and I prefer that (I like my reboots being without question a hardware-resetting power cycle :stuck_out_tongue: )

Unfortunately, I have tried both of these options and none of them work.

Same here, in my case the browser losses internet too and i am forced to shutdown with the power button. Book marked and i will share whatever i find on my own.

1 Like

I’m struggling with a similar issue. Did some research and I’m pretty sure it’s a bug in the current kernel. There seems to be fix for it already Bisected: drm/amd/pm: fixes a random hang in S4 for SMU v13.0.4/11 cause the issue the laptop doesn't repower after reboot or poweroff completely (#3351) · Issues · drm / amd · GitLab so just need to wait for it to hit the stable kernel release.

1 Like

How does one apply the fix to the kernel to fix this issue? I looked at what you linked but I’m still newby when it comes to linux.

Perform a full system update. I use the command line in a terminal with
sudo dnf upgrade --refresh

It seems the fix may not be made a part of the official repos because that didn’t update the kernel at all.

The kernel did not update, probably because it was already at the latest version. Any fixes would routinely be included by updates after testing.