Bug 12690

Summary: New Raspberry Pi 4 hardware boot loop
Product: IPFire Reporter: Craig Setera <craigjunk>
Component: ---Assignee: Arne.F <arne.fitzenreiter>
Status: CLOSED WORKSFORME QA Contact:
Severity: Major Usability    
Priority: - Unknown - CC: michael.tremer, peter.mueller
Version: 2   
Hardware: aarch64   
OS: Linux   
Attachments: Screenshot of boot loop

Description Craig Setera 2021-09-06 18:25:48 UTC 
Created attachment 936 [details]
Screenshot of boot loop

As part of the debugging of issue 12680, I've run into a boot loop on newer versions of Raspberry Pi 4 hardware.  Discussion to this point has taken place in the forum at https://community.ipfire.org/t/ipfire-2-27-core-update-159-raspberry-pi-4/6076/23.  As discussed there, with a keyboard and monitor attached to my Pi 4, I am able to get part way through the boot sequence before hitting a boot loop:

mmc1: Invalid bus width
mmc1: error -22 whilst initializing the SD Card
mmc1: Invalid bus width
mmc1: error -22 whilst initializing the SD Card
mmc1: Invalid bus width
mmc1: error -22 whilst initializing the SD Card

To validate that this is an issue with newer hardware, I was able to take advantage of another Pi 4 that is probably a year or so old in my Retropie setup.  I used that Pi and a Samsung 32G EVO SD card.  I tried the following combinations, all with a monitor and keyboard attached (and SERIAL set to off in uEnv.txt):

* RaspiOS - "old" Pi 4 - Works
* RaspiOS - "new" Pi 4 - Works
* IPFire - "old" Pi 4 - Works
* IPFire - "new" Pi 4 - Boot loops

As discussed in the forum thread, this looks suspiciously like an issue with U-Boot on newer Pi 4 hardware as discussed here:

* https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255080
* https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255080#c47
Comment 1 Craig Setera 2021-09-28 15:30:50 UTC 
I downloaded Ubuntu 20.04 image that uses u-boot and I'm seeing the same failure boot loop as on IPFire.  I will open a new ticket for u-boot.
Comment 2 Peter Müller 2021-10-23 11:27:06 UTC 
Since this is a problem in the U-Boot upstream, I am closing this. Please reopen if necessary.
Comment 3 Craig Setera 2021-10-23 16:49:00 UTC 
Does that mean that the fixes will automatically flow down to IPFire?  Are you aware of a specific fix in u-boot?
Comment 4 Michael Tremer 2021-10-25 12:39:06 UTC 
I would suggest keeping this open until there is a solution - even if the best person to work on this is on the RPi uboot team.

(In reply to Craig Setera from comment #1)
> I will open a new ticket for u-boot.

Could you link the bug report here?
Comment 5 Craig Setera 2021-10-25 13:31:38 UTC 
I should add that I was unable to figure out how to open a bug with u-boot.
Comment 6 Arne.F 2022-02-22 17:53:57 UTC 
I cannot reproduce this on my 8GB RPi4 which should also be the new hardware version.
I can boot core164 without problems from µSD and USB.
Comment 7 Peter Müller 2022-03-21 22:01:08 UTC 
Closing this as WORKSFORME then. Please reopen, if necessary.