On Tue, 2020-02-18 at 22:46 +0000, Peter Robinson wrote:
> 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?
No and no. You don't get that far you're dumped immediately into U-
Boot. You don't get a kernel menu.
Problem as been isolated to grubby creating a corrupted grub.cfg file.
Fixing that file has gotten all the damaged systems back up so fire
that I've fixed. Two systems I was able to kill -9 grubby and
immediately replace the grub.cfg file with a clean one and they
recovered. I've just got one dead one left that I have to pry the sd
card out of and edit the file on another system.
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.
I need to move to F-32 for sure and I definitely want the 5.5 kernel
for other reasons. My wife has a Lenovo Yoga 730-13 and the 5.4.*
kernels all barf with CPU lockup around the SSD card. Strangely, it
does with my Lenvo Yoga 730-15. But my 15" has a replacable SSD and
her 13" does not (that's on the only differences). But that's another
story. I've got an RPi-4 waiting for Fedora 32.
What other updates were in the list?
I'll have to dig that out of the logs. It's isolated to one of the
grubby scripts at this point.
Mike
--
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (c) +1 678 463-0932 |
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds. A pessimist is sure of it!