PC Won't Reboot/Restart [ Fedora 38 KDE ]

Ask Fedora
, , ,
1

Hello! I’m having a rather weird issue with my system and I am stumped on what to do.

I installed a new graphics card, and ever since, the system will not soft reboot/restart. It will begin the shutdown phase, but then it just shuts off. If I press the power button, it will flicker on for a second, and shut right back off.

To get it to power back up, I have to flip the power switch in back, hold the power button for a few seconds, flip the power switch back on, and then it will start up.

Specs:

AMD Ryzen 5 5600 CPU
AMD Radeon RX 6600 GPU
Gigabyte B450 DS3H Motherboard
64 GB DDR4 3200 RAM
1 TB NVMe M.2 SSD
Apevia Bronze 900w Power Supply
Fedora 38 KDE Linux OS

What I’ve tried:

I reseated the video card.
I have checked all cables and connectors.
I reinstalled Fedora (in case it was some weird driver conflict with the new card).

I’m not sure what else to try. Your help would be greatly appreciated. As it is, I get frequent updates that require a reboot, and I don’t want to damage the power supply by having to use the power switch in back to keep switching it on and off multiple times a week.

2

Can you get the logs from a prior boot where the issue occurred?
For example, if you restarted and it hung on the prior boot:
journalctl -b -1 -p 3 --reverse

That would output the journal from the prior boot, priority 3 (error) and lower, starting with the last entry.

3

Here is the first page of output from the latest incident:

Blockquote
Sep 18 22:31:34 Twilight-One kernel: watchdog: watchdog0: watchdog did not stop!
Sep 18 22:31:33 Twilight-One systemd-cryptsetup[31728]: Failed to deactivate: Device or resource busy
Sep 18 22:31:33 Twilight-One systemd-cryptsetup[31728]: Device luks-6aef5e19-df70-4942-ab24-8af21052e55d is still in use.
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:50 Twilight-One kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 21:29:26 Twilight-One kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2
Sep 18 20:24:34 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Sep 18 20:24:34 Twilight-One kernel: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 20:24:34 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Sep 18 20:24:34 Twilight-One kernel: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 20:24:34 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Sep 18 20:24:34 Twilight-One kernel: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 20:24:34 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Sep 18 20:24:34 Twilight-One kernel: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 20:24:34 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Sep 18 20:24:34 Twilight-One kernel: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 20:24:34 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Sep 18 20:24:34 Twilight-One kernel: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 18 20:24:34 Twilight-One kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Sep 18 20:24:34 Twilight-One kernel: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

It looks like it has something to do with luks?

4

Every one of those errors appears to be a problem with /dev/sr0 which would be your CD/DVD drive.

It is possible that in the process of replacing the GPU a cable to the optical drive may have been disturbed and now is causing errors in trying to configure the drive.

Check and reseat both ends of the cables to the optical drive and see if that helps.

It also may be that there is a disk in the drive that is not being read properly.

Only the lines at 1 1/2 minutes after the last errors on /dev/sr0 indicate a potential problem with luks and that seems related to the shutdown.

5

I removed the power and data cable to the CD drive (I’d been meaning to do that anyway as I don’t use it anymore). I did a full boot, and then restarted the system. Unfortunately, it did it again. Here is what I get from journalctl:

Blockquote
Sep 18 23:40:45 Twilight-One kernel: watchdog: watchdog0: watchdog did not stop!
Sep 18 23:40:45 Twilight-One systemd-cryptsetup[3610]: Failed to deactivate: Device or resource busy
Sep 18 23:40:45 Twilight-One systemd-cryptsetup[3610]: Device luks-6aef5e19-df70-4942-ab24-8af21052e55d is still in use.
Sep 18 23:39:33 Twilight-One konsole[3267]: kf.xmlgui: Shortcut for action “” “Show SSH Manager” set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Sep 18 23:39:33 Twilight-One konsole[3267]: kf.xmlgui: Shortcut for action “” “Show Quick Commands” set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Sep 18 23:39:26 Twilight-One dbus-broker-launch[1909]: Ignoring duplicate name ‘org.freedesktop.FileManager1’ in service file ‘/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service’
Sep 18 23:39:24 Twilight-One sddm-helper[1819]: gkr-pam: unable to locate daemon control file
Sep 18 23:39:16 Twilight-One dbus-broker-launch[1593]: Ignoring duplicate name ‘org.freedesktop.FileManager1’ in service file ‘/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service’
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ============================================
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Host ctl2: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Cmd: 0x0000371a | Max curr: 0x00c80064
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Caps: 0x31fe32b2 | Caps_1: 0x00004570
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Int enab: 0x00ff1083 | Sig enab: 0x00ff1083
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x0000fa07
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Present: 0x000f0000 | Host ctl: 0x00000001
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
Sep 18 23:39:15 Twilight-One kernel: mmc0: Got command interrupt 0x00080000 even though no command operation was in progress.
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ============================================
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Host ctl2: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Cmd: 0x0000371a | Max curr: 0x00c80064
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Caps: 0x31fe32b2 | Caps_1: 0x00004570
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Int enab: 0x00ff1083 | Sig enab: 0x00ff1083
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x0000fa07
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Present: 0x000f0000 | Host ctl: 0x00000001
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
Sep 18 23:39:15 Twilight-One kernel: mmc0: Got command interrupt 0x00080000 even though no command operation was in progress.
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ============================================
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Host ctl2: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Cmd: 0x0000371a | Max curr: 0x00c80064
Sep 18 23:39:15 Twilight-One kernel: mmc0: sdhci: Caps: 0x31fe32b2 | Caps_1: 0x00004570

I’m stumped. I have no idea what’s causing this.

6

Thanks for the update.
That seems to have stopped the errors noted above.

Please use the preformatted text tags with the </> button instead of the blockquote " button. It retains formatting and makes longer text quotes scrollable (both vertical and horizontal)

1 Like
7

I sure will. Sorry about that.

8

I did a restart just a few minutes ago, and this was the log:

Sep 19 15:12:00 Twilight-One kernel: watchdog: watchdog0: watchdog did not stop!
Sep 19 15:12:00 Twilight-One systemd-cryptsetup[23588]: Failed to deactivate: Device or resource busy
Sep 19 15:12:00 Twilight-One systemd-cryptsetup[23588]: Device luks-6aef5e19-df70-4942-ab24-8af21052e55d is still in use.
Sep 19 14:44:52 Twilight-One cupsd[1457]: [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost.
Sep 19 11:23:21 Twilight-One cupsd[1457]: [Client 2] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost.
Sep 19 10:48:24 Twilight-One systemd[1]: Failed to start dnf-makecache.service - dnf makecache.
Sep 18 23:46:30 Twilight-One konsole[3663]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Sep 18 23:46:30 Twilight-One konsole[3663]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Sep 18 23:46:17 Twilight-One dbus-broker-launch[1905]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
Sep 18 23:46:16 Twilight-One sddm-helper[1815]: gkr-pam: unable to locate daemon control file
Sep 18 23:46:10 Twilight-One dbus-broker-launch[1594]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
Sep 18 23:46:09 Twilight-One kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 9
Sep 18 19:45:58 Twilight-One kernel: usb 1-5: device descriptor read/all, error 8
9

The only thing I see that is common is the last 3 lines, and all seem related to shutting down. Don’t see anything about the startup failing. That log snippet seems to show parts of a 20 hour period.

Maybe showing a full log from an attempted boot that fails would give more info by getting that log from the prior failed boot immediately after a successful boot.

10

To start it back up, I have to shut it off at the power switch, otherwise it just sits there. The longest I let it sit was for about an hour, and it just did nothing but quietly run and the monitors had long since switched off.

This is how it happens every time, too. I press restart, the system goes through its normal shutdown procedure, and then right before it should switch to reboot, it just hangs there. So I click it off via the power switch in back, I hold down the front power button for a few seconds, and then when I flip the switch in back, it starts up.

It also does this if I’m restarting in the BIOS menu, like if I change settings, restarting does the same thing, and I have to go through the manual process.

I can show you a normal boot up if you like.

11

Today I powered everything off, opened the system and went through each and every connection, seeing if one of them was causing the failure to shutdown and restart. By the end, the system was still hanging on shut down and I would have to manually switch it off in back, press the front power button for a few seconds, and then flip the switch in back and it would start up again.

I’m just not sure what else I can do. From the log, it looks like LUKS is preventing a shutdown because a device isn’t being released, but I removed the hard drive and tested it in the BIOS, and it still hung on restart, so it’s either something with the power supply, or maybe the video card? I have no way of testing if it’s the video card because I don’t have onboard video, and I don’t know anyone who would let me borrow theirs.

Honestly, the power supply would be the easiest to take care of, I can get one relatively cheap. I could probably get a $30 AMD graphics card and test if that’s the source of the issue, but I’m hoping to solve this without having to put more money into it.

Still, I appreciate all of the responses, and I hope maybe I can get this sorted out. I love Fedora, but it’s very much a distro that likes to restart after updates, and for good reason.

12

I disagree with that statement.
The only time I need to restart is when there is a kernel update, a DE update, or a driver update for the GPU.

I have done almost all other updates without restarting and very seldom have an issue.

Yes, if you allow the system to perform the automatic (offline) updates it often does a restart, but that seems more of a safety net than necessity in most cases.