Sometimes my Fedora 40 doesn’t turn off until the end. During such an unsuccessful shutdown, the screen goes out, ssh and sunhine servers become unavailable, but the hardware does not turn off. I’ve been waiting for over 20 minutes, but it doesn’t help.
I can’t reproduce the problem on purpose, but it occurs periodically. The LED near the power button is on, the fans of the processor and video card are spinning. Forced shutdown via the power button of the system unit helps
How can I analyze this situation?
I am a novice fedora and linux user. Less than 10 days have passed since the installation of the system, if this information is relevant.
This command displays the logs for the current boot session -b with the last entry at the bottom -1 . Look for any errors or warnings around the time you attempted the shutdown.
You can also try during a problematic shutdown, pressing the Esc after initiating the shutdown process. This might reveal messages on the screen indicating what’s causing the issue.
It sounds like a service is taking long to shut down, and holds the shutdown process up in the meantime. As a random guess, maybe a device on your LAN is keeping Sunshine active until that device closes the connection (maybe it’s Android and it keeps it open for a bit regardless of it not being in Recents).
During the long shutdown, try disconnecting the internet (unplug Ethernet or temporarily power-off wifi router); if it shuts down instantly after that, it’s likely a service keeping or having a connection active.
A very interesting assumption.
I tried to reboot fedora through an active session in sunshine, but the system rebooted successfully. Maybe this situation happens sometimes, I don’t know. There have been no unsuccessful shutdowns recently. I’ll try to read the system logs.
I didn’t found anything interestings in the systems log, except one error, but it repeats every shutdown:
ая 10 21:15:43 fedora systemd[1]: Using hardware watchdog 'iTCO_wdt', version 4, device /dev/watchdog0
may 10 21:15:43 fedora systemd[1]: Watchdog running with a timeout of 10min.
may 10 21:15:43 fedora kernel: watchdog: watchdog0: watchdog did not stop!
may 10 21:15:43 fedora systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 4, device /dev/watchdog0
may 10 21:15:43 fedora systemd-shutdown[1]: Watchdog running with a timeout of 10min.
may 10 21:15:43 fedora systemd-shutdown[1]: Syncing filesystems and block devices.
may 10 21:15:43 fedora systemd-shutdown[1]: Sending SIGTERM to remaining processes...
may 10 21:15:43 fedora systemd-journald[664]: Journal stopped
I will try to enter “ESC” in the next problematic shutdown.
Same problem here since I switched from Geforce to Radeon this year in February. However, for me it’s not only when shutting down, but also when switching to suspend. Under Fedora 39 with kernel 6.7 it happened every few days, since Fedora 40 and kernel 6.8 it only happens about every ten days. Then it is exactly as you describe: The system seems to shut down completely, only the power LED stays lit and the fans keep spinning. If I want to switch the computer off completely, I have to force-shutdown with the powerbutton.
I really don’t know what the exact reason for this behavior could be, but since the last kernel updates and the associated AMD updates have definitely made a difference, I think we’ll have to wait patiently for the next updates. Until then I will also keep an eye on the logs and the shutdown process and post here if I find out anything.
Phoronix said a few weeks ago that kernel 6.10 is coming with more AMD updates, as you can read here:
There are also some fixes there, I’ll keep my fingers crossed!
Mainboard ASUS PRIME Z370-A RAM 32,0 GiB CPU Intel Core i5-8600 GPU AMD Radeon RX7600XT OS Fedora Linux 40.20240516.0 (Silverblue) GNOME 46 Window-Manager Wayland Kernel-Version Linux 6.8.9-300.fc40.x86_64
Thanks for your reply!
Sadly i got only the current Kernel in my kernel-list.
Reverting to an earlier kernel version probably won’t help, as this problem has existed for me since I’ve had an AMD GPU and that’s since about kernel 6.7.6 and fedora silverblue 39.
Thanks for the tip! I’ll see if i can switch to a kernel older than 6.7 when i get the chance. Currently i’ll test whether the problem will also occur under xorg.
The Linux kernel has been updated to 6.8.10, video card drivers and some libraries. The system does not start on the new core. It hangs in grub at the “Loading Linux 6.8.10” stage. It does not respond to ESC.
On the other hand, now EVERY system shutdown from kernel 6.8.9 does not complete successfully. The ESC key does not lead to anything. I have no idea what to do about it.
I like my next attempt to upgrade to Linux from Windows, but this problem bothers me.
UPDATE:
The computer successfully turns on and off on the 6.8.8 core. Perhaps there are some problems with the new cores for my hardware.
Your issue might be different thant what the OP experienced. We have found that reinstalling the kernel has helped some people. Also, using the ESC is not relevant to your system as you are probably using Grub as the default bootloader. If you are still experiencing issues please start a new thread.
