I have one completely stock workstation F32 machine where kernel updates
almost always cause a multiple-reboot panic problem. This problem also
occurred on F31, but not on releases before that. I'm stumped and need
some help in figuring it out.
The symptoms vary in the number of reboots and the type of tertiary
error, but are otherwise pretty similar. It does not matter whether I
use the Gnome update app or the CLI dnf method. After a number of
reboots, the upgrade succeeds and Fedora behaves nortmally again. I
think that this only happens whenever the kernel is upgraded.
What I observe is that the machine is rebooted and on reboot, grub (I
think) gets a halt for a 32-bit relocation error. This sequence may
happen twice. Its an i7 with plenty of memory and an SSD boot disk, so
the 32-bit thing is confusing. To get around this error, I powercycle
the box and get into the next stage of the problem. One the 2nd or 3rd
reboot, I usually see a halt with an access outside of the kernel space,
although with the update this morning, I had a kernel panic instead.
Cold-booting again, and the update is installed, and the last reboot and
I'm up on the new updates.
After that, the machine behaves normally until the next kernel updates.
I assume that there is some incorrectly-asynchronous operation in grub
related to the update entry, but I can find no grub logs to dig into
this problem. I have several other machines that do not see this
problem. I dug around in the fedora bugs, but not knowing what to look
for, I'm basically blind. Its a pretty serious bug, especially if the
machine is remote. Does anyone have a way out of this?
--
John Mellor
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
