I have a fair number of Raspberry Pi V3 B/B+ and Raspberry Pi V2 B
systems running Fedora 31 (and a V4 I would like to get on Fedora -
still waiting). I have Fedora 31 aarch64 installed on most of the V3
and armv7l/armhfp on the V2 systems. Running dnf updating today,
updated to the 5.4.19 kernel and the update of the aarch64 images
seemed to hang while running the kernel-core script for over an
hour. Looking from another terminal and running top (running dnf
upgrade remotely over ssh), looks like grubby is hung burning CPU time
and eating memory (and I have lots of cache). Couple machines
eventually crashed, and I killed grubby on a couple of others, and the
dnf eventually ran to completion on the later 2. In all cases (5 -
aarch64 systems) I was left with totally unbootable systems. The ones
with screens go straight to the U-Boot prompt or trying to reboot over
and over again looking for storage and then looking at eth0 and then
rebooting and never show the kernel selection prompt. The few
armv7l/armhfp systems haven't seem to have gotten that the 5.4.19
upgrade yet. I've still got two booted and running aarch64 systems
running (haven't rebooted) and I'm going to try and roll that update
back.
Any thoughts to were to go from here? Not sure what to report this
under in Bugzilla.
You should at lest be able to select the prior kernel from the menu.
Was is the same update on aarch64 and ARMv7?
I'm not aware of any issues but I think all my RPi testing has moved
to F-32 or at the very least to 5.5 or later kernels.
What other updates were in the list?