RPi3 boot failure with r325156 snapshot

[Richard Perini]

On Mon, Nov 06, 2017 at 06:50:49PM -0500, Hyun Hwang wrote:
> Hello,
> 
> I tried to boot RPi3 with -CURRENT snapshot (r325156), but it failed. I doubt this boot failure is related to the [issue](https://lists.freebsd.org/pipermail/freebsd-arm/2017-November/016986.html) discussed earlier in this list since it just gives up even before the kernel is loaded by the EFI loader (if I guessed it correctly). I tried all the available snapshots---r323985, r324306, r324542, and r324754---on the download server, but no success so far.
> To see if this is caused by hardware problem I tried few tests on Raspbian Stretch and found out that the hardware is just fine.
> 
> Here is the entire log appeared on screen, in case anyone finds this helpful:
> ```
> Net:   Net Initialization Skipped
> No ethernet found.
> starting USB...
> USB0:   Core Release: 2.80a
> Scanning bus 0 for devices... 4 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
>        scanning usb for ethernet devices... 1 Ethernet Device(s) found
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current devices
> Scanning mmc 0:1...
> Found EFI removable media binary efi/boot/bootaa64.efi
> reading efi/boot/bootaa64.efi
> 82224 bytes read in 35 ms (2.2 MiB/s)
> ## Starting EFI application at 01000000 ...
> Scanning disks on usb...
> Scanning disks on mmc
> Adding logical partition
> Adding logical partition
> MMC Device 1 not found
> MMC Device 2 not found
> MMC Device 3 not found
> Found 7 disks
> ???[18t???[?25h???[2J
> >> FreeBSD EFI boot block
>    Loader path: /boot/loader.efi
>    
>    Initializing modules: ZFS UFS
>    Loader path:
> "Synchronous Abort" handler, esr 0x96000004
> ELR:     3af62cec
> LR:      3af61d60
> x0 : 0000000000000000 x1 : 0000000000000000
> x2 : 000000003afeb000 x3 : 0000000000000000
> x4 : 000000003ab2eec0 x5 : 0000000000000000
> x6 : 0000000000000015 x7 : 0000000000000000
> x8 : 000000003af72eb0 x9 : 0000000000000000
> x10: 0000000000000068 x11: 0000000000000040
> x12: 0000000000000000 x13: 0000000000000000
> x14: 0000000000000000 x15: 0000000000000000
> x16: 0000000000000000 x17: 0000000000000000
> x18: 000000003ab30df8 x19: 0000000000000000
> x20: 0000000037a16008 x21: 000000003af86f74
> x22: 0000000039b2ddd8 x23: 00000000000007d0
> x24: 0000000039b2dde0 x25: 0000000039b2ddd0
> x26: 000000003af83ac0 x27: 0000000039b1be1c
> x28: 0000000039b2ddc8 x29: 000000003ab2ef60
> 
> Resetting CPU ...
> 
> resetting ...
> ```
> 
> In the meantime, I will try to build my own snapshot using r325364---mentioned [here](https://lists.freebsd.org/pipermail/freebsd-arm/2017-November/017000.html)---if it's possible to cross-build on i386.
> 

Ditto - I found the same issues last night.  I've been unable to build a
working image with r325420.  I was able to boot the most recent RaspBSD 
image which appears to be r320146.

--
Richard Perini  
Ramico Australia Pty Ltd   Sydney, Australia   rpp at ci.com.au  +61 2 9552 5500
-----------------------------------------------------------------------------
"The difference between theory and practice is that in theory there is no
 difference, but in practice there is"