The notebook has a full-sized SD card reader, but it’s empty and I’m pretty sure it was never ever used, I I do not have such a card and cannot remember I could use in at any device.
I found a similar question on AskUbuntu. If you don’t use the SD card reader at all, the suggested solutions are to either disable it in the BIOS/UEFI configuration, or blacklist the sdhci kernel module.
Before doing that, you can unload the module first, to test if it solves the problem:
sudo modprobe -r sdhci
Then, shutdown and see.
If it works, you can blacklist the module (copy and paste the whole block into terminal):
The first step to help others with the same hardware would be to provide your hardware details.
Adding your system to the Linux Hardware.org database and adding the link here could help users of other distros.
% modinfo sdhci
filename: /lib/modules/6.2.12-300.fc38.x86_64/kernel/drivers/mmc/host/sdhci.ko.xz
license: GPL
description: Secure Digital Host Controller Interface core driver
author: Pierre Ossman <pierre@ossman.eu>
depends: mmc_core
retpoline: Y
intree: Y
name: sdhci
vermagic: 6.2.12-300.fc38.x86_64 SMP preempt mod_unload
sig_id: PKCS#7
signer: Fedora kernel signing key
[...]
parm: debug_quirks:Force certain quirks. (uint)
parm: debug_quirks2:Force certain other quirks. (uint)
sdhci.h defines dozens of quirks. Normally the driver should query the hardware to determine what is needed. Using sdhci debug quirks may be needed when sdhci logic fails.
What is the full name and ID (xxxx:xxxx) of your SD card reader? Check lsusb and lspci -nn.
Search for bugs first in Fedora bug tracker, since you are using Fedora packaged kernel (I assume). I found 1 similar report although it’s old and the symptoms are different, so you should probably file a different report.
Use lsmod | grep -F sdhci to find modules that use sdhci, make a list, and try to remove everything that uses sdhci. If your reader is a PCI device, you should see sdhci_pci so you would try: sudo modprobe -r sdhci_pci sdhci.
I’m not sure what this means – are you updating using the Gnome Software app or command-line? Using the Gnome Software app they system restarts, updates, and restarts a second time again. Applying updates can take a long time especially if 3rd party modules needs compiling. I always remove “rhgb quiet” from the kernel command-line so I can monitor updating progress (I seldom reboot unless updating).
Updating using standard KDE GUI program. It downloads updates, then restarts, then installs updates (with progress bar, can press Esc and see %%), then it restarts again (at this stage I have the problem).