[fedora-arm] Re: Failures booting on Pi4

[Steven A. Falco]

On 7/18/22 03:26 PM, Chris Adams wrote:
>  Once upon a time, Steven A. Falco <stevenfalco(a)gmail.com&gt;
> said:
> > So, there is something bizarre happening with uSD cards with most of the images I
> tested.  The only image that works for me on a uSD card is the Server image.  Note that I
> tried several different uSD cards - Samsung, SanDisk, and a "no name" card, and
> got consistent results, so I don't think the uSD cards are at fault.
>  
>  If you take off "rhgb quiet" from the kernel command line, do you see
>  kernel error messages?  If I try to boot Fedora on a Pi 4B with any card
>  in the uSD slot, I get a loop of these from the kernel:
>  
>      mmc0: error -22 whilst initialising SD card
>      mmc0: invalid bus width 
Interesting.  I get an mmc0 error, but it looks different.  I get this in a loop:

[   51.973829] mmc0: ADMA error: 0x02000000
[   51.982126] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[   51.993799] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[   52.005088] mmc0: sdhci: Blk size:  0x00007008 | Blk cnt:  0x00000001
[   52.016654] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000013
[   52.028282] mmc0: sdhci: Present:   0x1fff0206 | Host ctl: 0x00000011
[   52.039924] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[   52.051544] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000a707
[   52.063216] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[   52.074896] mmc0: sdhci: Int enab:  0x03ff100b | Sig enab: 0x03ff100b
[   52.086568] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[   52.098224] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[   52.109936] mmc0: sdhci: Cmd:       0x0000333a | Max curr: 0x00080008
[   52.121629] mmc0: sdhci: Resp[0]:   0x00000920 | Resp[1]:  0x00ee7f7f
[   52.133368] mmc0: sdhci: Resp[2]:   0x325b5900 | Resp[3]:  0x00400e00
[   52.145037] mmc0: sdhci: Host ctl2: 0x00000008
[   52.154607] mmc0: sdhci: ADMA Err:  0x00000001 | ADMA Ptr: 0xe7000200
[   52.166233] mmc0: sdhci: ============================================
[   52.177916] mmc0: sdhci: e7000200: DMA 0xf4802000, LEN 0x0008, Attr=0x21
[   52.189979] mmc0: sdhci: e7000208: DMA 0x00000000, LEN 0x0000, Attr=0x03
[   52.203909] mmc0: error -5 whilst initialising SD card

>  I'm not sure how you'd get different behavior with different
> images
>  though, because they're all the same kernel/initrd setup AFAIK 
They are mostly
the same setup, but perhaps there are some race conditions that are triggered by the
different filesystems that the different image types use?  I know that Minimal uses ext4
for /, Workstation and KDE use btrfs, and Server uses lvm + xfs.

Since the USB flash sticks are well-behaved I'll use them for now.  But this is one
quirky piece of hardware, and I'm not surprised it has taken so many people so many
hours/years to get it to work at all.

I haven't posted the following as a bug yet, but when I ssh into the unit as root I
get an oops as shown in the attached file.  But if I ssh into the unit as a normal user,
there is no oops.  The oops is non-fatal, as far as I can tell, but unsettling
regardless.

	Steve