Re: arm 32 bit fedora quit booting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for the answer about libzstd. On 27 Dec I also had a problem with booting my Odroid XU4. However I needed that system back up and running so I didn't dig too much into what was wrong, I just knew it was one of the recent updates. Probably was that libzstd bug as that was in the list of updates which did break things for me.


Michael Whapples

On 30/12/2021 00:39, Kevin Fenzi wrote:
On Wed, Dec 29, 2021 at 07:08:19PM -0500, Jeffrey Walton wrote:
On Wed, Dec 29, 2021 at 2:34 PM Timothy Krantz
<tkrantz@xxxxxxxxxxxxxxxxxx> wrote:
I have several 32 bit arm machines running fedora 35.  I update them via dnf on an almost daily basis.

Yesterday afternoon I had a brief power failure and now none of them will boot or boot into an unusable state.  At first I suspected the power blip was the culprit but now I am not so sure.  I am getting similar behavior on all of them.

Here is a capture of my wandboard quad :

https://pastebin.com/fVQYCXML

The first thing that I see that looks bad is about 26 seconds in :

[   26.070965] systemd-journald[234]: Received SIGTERM from PID 1 (systemd).

But maybe that is a red herring.  Things do go south from there.

Similar issues on a lime2 and a ras pi running 32 bit code.

Any suggestions would be appreciated.
It sounds like a hardware problem due to the earlier power problems.
There's no way a software update could be interrupted at the same
point on several machines, and produce the same exact error during
boot on those machines.

Check the power warts. They are cheap and go bad on their own. They
don't need a power surge or brownout to smoke them. That you had a
[significant enough] power event was probably more than enough to
break them.

Or, check your power distribution strip if the machines are plugged
into the same strip.
Might be:

https://bugzilla.redhat.com/show_bug.cgi?id=2035802

(ie, libzstd breaking things, try downgrade/upgrading?)

kevin

_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-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/arm@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-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/arm@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux