On Tue, 2020-02-18 at 19:44 -0500, Stuart D. Gathman wrote:
> On Tue, 18 Feb 2020, Michael H. Warfield wrote:
>
> > So the problem is in grubby. This had to have happened in just the
> > last week. The update to 5.4.18 did not result in this
> > carnage. So,
> > whatever happened with grubby happened recently.
> > Strangely, the /boot/efi/EFI/fedora/grub.cfg file is in the aarch64
> > image but not in the arm7l image. :-?
> It seems like this bug would affect all EFI systems, not just
> aarch64.
> I'm be on the alert before installing 5.4.19 on x86_64 as well.
I agree. Seems strange but...
I'm actually wondering if the hang and crash is a buffer overrun. I
looked on a newly rebuilt system and saw the corruption but it was only
a few lines long and the system still worked. I've got a pile of
development systems are updated every time a kernel gets updated (once
or twice a week) that that line had hit over 800K long. They're all
largely mirrors of each other, just with different tasks. Each of the
"corrupt" files were identical but all of the updates have been in lock
step.
All but one of the six affected systems are back up and the single one
that's not managed to boot the kernel and started but ran into a panic.
But I get a kernel menu on it now.
Just checked my x86_64 system (a Lenovo Yoga 730-15). No sign of the
corruption in that file. Very strange but 6 systems impacted at nearly
the same time (hours).
Mike
--
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 | mhw@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!
No comments:
Post a Comment