Re: Unable to boot Pi 3b+ [crashes during bcm_sdhci_attach for Broadcom 2708 SDHCI controller for modern RPi* firmware]

From: Mark Millard <marklmi_at_yahoo.com>
Date: Sat, 19 Aug 2023 19:12:52 UTC
On Aug 19, 2023, at 11:59, Peter G <list-freebsd-arm@box559.com> wrote:

> Mark Millard wrote on 2023-08-19 02:14:
> [...]
>> The thing to log would probably be a boot attempt of a fresh
>> 13.2-RELEASE that has had the RPi* firmware ( including
>> bcm271*.dtb files and overlays/ ) from 14.0-ALPHA2 (or ALPHA1)
>> substituted, probably also having had u-boot.bin substituted.
>> In other words, avoiding having any old vintages of those
>> materials. I'd suggest leaving EFI/ and dtb/ alone. Those have
>> files built as part of FreeBSD.
>> If nothing else, this could help with identifying analogous
>> contexts in the future if others have problems.
>> ===
>> Mark Millard
>> marklmi at yahoo.com
> 
> I copied these files
>  start*.elf
>  fixup*.dat
>  bcm*
>  overlays/*
>  u-boot.bin
> from
>  FreeBSD-14.0-ALPHA2-arm64-aarch64-RPI-20230818-77013f29d048-264841.img
> to
>  FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img
> and booted the modified image.
> 
> The crash is back. The console log is at:
>  https://box559.com/console-13.2-RELEASE-mod4.txt
> 

Thanks.

To publicly/broadly publish the crash material part of that log file:

. . .
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 17 on simplebus0
Fatal data abort:
  x0:         ffffffff
  x1:                0
  x2: ffff0000008d6ebe
  x3:               6e
  x4: ffff000000f4060c
  x5:               6e
  x6: ffff0000001927a8
  x7: 6d63625f69636864
  x8: ffff000000e34700
  x9:               20
 x10:                0
 x11:                1
 x12:  300000000006e65
 x13:   fefefefeff0100
 x14:              69b
 x15:               1a
 x16:                0
 x17:                0
 x18: ffff000000f407e0
 x19:         ffffffff
 x20:                0
 x21: ffff000000be6000
 x22: ffff000000be6000
 x23: ffffa00000ddec38
 x24: ffff000000938016
 x25: ffff000000961e00
 x26: ffff0000008f9bfb
 x27: ffffa00000dced60
 x28:         31e00000
 x29: ffff000000f407e0
  sp: ffff000000f407e0
  lr: ffff000000880e04
 elr: ffff00000087aefc
spsr:         a00000c5
 far:               20
 esr:         96000004
panic: vm_fault failed: ffff00000087aefc
cpuid = 0
time = 1
KDB: stack backtrace:
#0 0xffff0000004fd02c at kdb_backtrace+0x60
#1 0xffff0000004a8328 at vpanic+0x13c
#2 0xffff0000004a81e8 at panic+0x44
#3 0xffff0000007f42e0 at data_abort+0x200
#4 0xffff0000007d3010 at handle_el1h_sync+0x10
#5 0xffff000000880e00 at bcm_sdhci_attach+0x318
#6 0xffff000000880e00 at bcm_sdhci_attach+0x318
#7 0xffff0000004e8f94 at device_attach+0x3fc
#8 0xffff0000004eb134 at bus_generic_new_pass+0x120
#9 0xffff0000004eb0c4 at bus_generic_new_pass+0xb0
#10 0xffff0000004eb0c4 at bus_generic_new_pass+0xb0
#11 0xffff0000004eb0c4 at bus_generic_new_pass+0xb0
#12 0xffff0000004ed200 at root_bus_configure+0x40
#13 0xffff00000041e5e8 at mi_startup+0x11c
#14 0xffff0000000008b4 at virtdone+0x78
Uptime: 1s



===
Mark Millard
marklmi at yahoo.com