My Fedora WS 42 doesn’t shut down or reboot in any way I can think of, and it creates a whole lot of problems. It comes to:
" . . . [ XXX.XXXXXX (some number, not allways the same) watchdog: watchdog did not stop!] processing ?????-3444 is taking a long time",
and it stucks there until I turn the computer off by the power switch. When I turn it on again, it behaves in many different ways, but mostly comes in very low resolution up to:
"[ XXX.XXXXXX (some number, not allways the same)] (udev-worker)[XXX (some number, not allways the same)] note: exited with irqs dissabled
"[ XXX.XXXXXX (some number, not allways the same)] (udev-worker)[XXX (some number, not allways the same)] note: exited with preempt_count 1"
and it stucks there until I turn the computer off by the power switch. At that point, my keyboard either works or doesn’t, but the system doesn’t react on any keystroke.
If I restart it again, and chose “System Repair” from UEFI menu, it behaves in many different ways again:
* Sometimes it makes a step or two more, so that the "note: exited with preempt_count 1" is not the last line, and it stucks there until I turn the computer off by the power switch,
* sometimes it comes to Fedora logo in very low resolution, and it stucks there until I turn the computer off by the power switch,
* sometimes it comes to black screen, and it stucks there until I turn the computer off by the power switch
* . . .
If I play with UEFI menu items, like “Diagnostics”, “ME Setup”, “Network Boot” (There is nothing to boot from on my home network, but it gives me oportunity to reboot by “Ctrl-Alt-Delite”), … , sometimes it comes to Fedora logo in normal resolution, and sometimes it doesn’t.
If it doesn’t, and I press the Esc key, the last lines are either:
"[ --*-- ] Job systemd-udev.service/stop running (XXs/XXs) Shutting down...
BUG: unable to handle page fault for address: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same)
uPP: supervisor write access in kernel mode
. . .
[ OK ] Reached target initrd-switch-root.target - Switch Root
Starting initrd-switch-root.services - Switch Root..."
or:
"RSP: HHHH:HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) EFLAGS: XXXXXXXX (some number, not allways the same) ORIG-RAX: XXXXXXXXXXXXXXXX (some number, not allways the same)
RAX: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) RBX: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) RCX: (some hexadecimal number, not allways the same)
RDX: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) RSI: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) RDI: (some hexadecimal number, not allways the same)
RBP: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) R08: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) R09: (some hexadecimal number, not allways the same)
R10: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) R11: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) R12: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same)
R13: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) R14: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same) R15: HHHHHHHHHHHHHHHH (some hexadecimal number, not allways the same)
</TASK>"
and it stucks there until I turn the computer off by the power switch, but sometimes it boots up to the normal desktop and, from that point on, it works normally untill I try to shut it down or the system wants to reboot after it downloaded some updates that want it to reboot.
If the system comes to Fedora logo in normal resolution and it stucks there, and I press the Esc key, I can see some interesting lines:
1. ICU: INFO: ICU_prompt self-detected stall on CPU
ICU: 3=....1 (59999 ticks this GP) idle=931c/1/0xXXXXXXXXXXXXXXXX (some number, not allways the same) softirq=1558/1569 fqs=14999
ICU: (t=60000 jiffies g=961 q=357 ncpus=4)
2. fedora systemd[1791]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-1929.scope - Application launched by gnome-session-binary.
3. </TASK>
watchdog: BUG: soft-lockup - CPU#3 stuck for XXs! (some number, not allways the same) [modprobe: XXX (some number, not allways the same)]
CPU#3 Utilization every 4s during lockup:
#1: 100% system, 0% softirq, 1% hardirq, 0% idle
#2: 100% system, 0% softirq, 0% hardirq, 0% idle
#3: 100% system, 0% softirq, 0% hardirq, 0% idle
#4: 100% system, 0% softirq, 0% hardirq, 0% idle
#5: 101% system, 0% softirq, 1% hardirq, 0% idle
If there was some update to be installed after reboot, sometimes I managge to come to:
"Installing updates - 100%
. . . [ XXX.XXXXXX (some number, not allways the same) watchdog: watchdog did not stop!] processing ?????-3444 is taking a long time"
or even to:
"systemd-shutdown[1]: Rebooting"
but it doesn’t reboot, and it stucks there until I turn the computer off by the power switch. After that, if I manage to reach the desktop, the updates are installed.
It all started after an update in july, and since then I was hopeing it will be corrected with the next update, but it’s still here. Please, is there anything I can do or, at least, is there a correct way to start the system after hard switch off so that I don’t wonder with UEFI menu, trying and failing, and not realy knowing what I was doing.
My computer is:
Hewlett-Packard ProDesk 600 G1 SFF, Product Family 103C_53307F G=D
Motherboard 18E7, Asset Tag 2UA52619T0
BIOS Release 2.75, version L01 v02.75 from 05/04/2018
Processor: Intel(R) Core™ i5-4570 CPU @ 3.20GHz
RAM: 16GB @ 1.6 GHz
Kernel Release: 6.16.11-200.fc42.x86_64, Version: #1 SMP PREEMPT_DYNAMIC Mon Oct 6 20:00:39 UTC 2025
(but it was all the same with earlier versions since july)
GNOME 47, if I’m not misstaken.
