Hi I use Fedora KDE and recently upgraded to fedora 44 but started experiencing this issue even before a full system upgrade, just with fed44 packages installed. But the issue has persisted even after a full system upgrade. Every time I go to shutdown my PC is hangs with a code 05 error on my motherboard LED indicator, even if I haven’t been doing heavy workloads. The only work around I found to work at the moment is to restart my PC which I assume flushes out any background services and lets me clean shutdown with no hang.
I’ve tried the following fixes:
- Stopping watchdog service (previous journalctl check showed that watchdog did not stop)
- Letting the system rest with programs shutdown for 10+ minutes
- XMP profile 1 set, with reduced MT/s to 5600 rather that full 6000
- I also checked desktop environment factors because I noticed some gnome packages were installed with the upgrade, not sure what it would affect exactly though and if it relates to this issue.
I havent changed any ACPI settings other than adding this to /etc/systemd/system/:
[Unit]
Description=Disable all ACPI wake devices
[Service]
Type=oneshot
ExecStart=/bin/sh -c ‘for i in $(cat /proc/acpi/wakeup | grep enabled | awk “{print $1}”); do echo $i > /proc/acpi/wakeup; done’
[Install]
WantedBy=multi-user.target
because originally I experience an issue with my PC waking immediately after shutdown even if I didn’t activate it.
I also currently run a dual boot setup with Fedora as my main (grub in use) and Windows as a secondary OS, but this issue does not occur when I use Windows.
Not sure what to do, and I don’t want to break anything too much.
For other details my relevant hardware includes:
Aorus Gigabyte z890 elite
Core Ult 7
Kingston Fury Beast 64gb RAM
AMD Radeon rx 9070 xt swift
Thank you
What is a “code 05 error”? Can you show the output where you’re seeing this “code 05 error” as frankly it could be anything.
If you actually mean it’s a code displayed by the LED indicator on the motherboard itself, you should be able to find the precise meaning of that code in your manual. They usually appear on POST though, rather than on Operating System shutdown.
If this code is in a log, such as journalctl then you’ll need to post the relevant section of your journalctl output.
Sorry, I should have specified it as “Motherboard LED indicator” this code 05 indicates a memory initialization failure. But like I said, I believe its being cause by fed44 because I never had this issue with 43 a couple weeks ago and it doesnt happen with Windows.
I’d be surprised if a memory init failure occurred at shutdown and even more surprised if an operating system had any means to set or trigger POST codes on a motherboard but regardless, what do you have in journalctl for the shutdown process?
Here’s what I got running journalctl -b -1 -e
Jun 12 19:02:04 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor >
Jun 12 19:02:04 fedora systemd[1]: Reached target shutdown.target - System Shutdown.
Jun 12 19:02:04 fedora systemd[1]: Reached target final.target - Late Shutdown Services.
Jun 12 19:02:04 fedora systemd[1]: systemd-poweroff.service: Deactivated successfully.
Jun 12 19:02:04 fedora systemd[1]: Finished systemd-poweroff.service - System Power Off.
Jun 12 19:02:04 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-powe>
Jun 12 19:02:04 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-power>
Jun 12 19:02:04 fedora systemd[1]: Reached target poweroff.target - System Power Off.
Jun 12 19:02:04 fedora systemd[1]: Shutting down.
Jun 12 19:02:04 fedora audit: BPF prog-id=63 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=62 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=45 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=47 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=46 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=79 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=78 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=61 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=60 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=53 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=52 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=67 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=66 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=48 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=50 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=49 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=57 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=56 op=UNLOAD
Jun 12 19:02:04 fedora audit: BPF prog-id=41 op=UNLOAD
Jun 12 19:02:04 fedora systemd-shutdown[1]: Syncing filesystems and block devices.
Jun 12 19:02:04 fedora systemd-shutdown[1]: Sending SIGTERM to remaining processes…
Jun 12 19:02:04 fedora systemd-journald[954]: Received SIGTERM from PID 1 (systemd-shutdow).
Jun 12 19:02:04 fedora systemd-journald[954]: Journal stopped
Watchdog isn’t running anymore because I stopped it, but before it would say “Watchdog did not stop” error.
Also regarding the 05 error code, its just what I have to go off of from the hardware side, I don’t have enough experience to pinpoint exactly what it might be. All I can say is, the system goes to shutdown, my peripherals stop receiving a signal (no monitor output at all either), but my gpu, fans, motherboard and in tower hardware continue to run.
First thing I’d do is to check the BIOS version you’re running (inxi -F will tell you the version) and make sure it’s up-to-date with the latest version provided by the motherboard supplier.
My BIOS is up-to-date, I updated to F20a.
I have been testing for a bit and I just picked up, it actually only hangs when the pc has been in sleep mode and the wakes again.
Another note on that, although I’m not sure how relevant… usually when I boot I get code b1 on my motherboard, but when I sleep the pc it posts code 00, then when I wake it again, it stays as code 00.
You’ll have to look those code up in your manual and determine what the correct modus operandi is.
We have no idea what the normal status codes would be - I’d expect 00’s all round to be honest.
I don’t know why you would see a memory init error on shutdown and not startup, but I’d suggest running a memory tester such as memtest86+ to make sure your memory/RAM/DDR is solid.