Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Nov 2017 12:18:40 -0800
From:      Mark Millard <markmi@dsl-only.net>
To:        Richard Perini <rpp@ci.com.au>, Hyun Hwang <hhwang@sent.com>, freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: RPi3 boot failure with r325156 snapshot
Message-ID:  <CA12A234-A3D1-4EC1-8BA1-49E646A356E9@dsl-only.net>
In-Reply-To: <20171107091135.GA37713@jodi.ci.com.au>
References:  <1510012249.2152828.1163794192.4049F0E8@webmail.messagingengine.com> <20171107091135.GA37713@jodi.ci.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Nov-7, at 1:11 AM, Richard Perini <rpp at ci.com.au> wrote:

> On Mon, Nov 06, 2017 at 06:50:49PM -0500, Hyun Hwang wrote:
>> Hello,
>>=20
>> 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/0169=
86.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.
>>=20
>> 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
>>=20
>>   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
>>=20
>> Resetting CPU ...
>>=20
>> resetting ...
>> ```
>>=20
>> In the meantime, I will try to build my own snapshot using =
r325364---mentioned =
[here](https://lists.freebsd.org/pipermail/freebsd-arm/2017-November/01700=
0.html)---if it's possible to cross-build on i386.
>>=20
>=20
> 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=20
> image which appears to be r320146.

It looks like -r325093 introduced a loader build
problems when it switched to using bsd.init.mk
instead of src.opts.mk in various places, including
sys/boot/efi/loader/Makefile . It is not limited
to aarch64 contexts or to efi contexts, although
the details likely would vary.

The issue is now addresses by -r325556 , see:

=
https://lists.freebsd.org/pipermail/svn-src-head/2017-November/105958.html=


If that is a sufficient fix for building for
the Pine64 family I do not know. But it
might be involved.

=3D=3D=3D
Mark Millard
markmi at dsl-only.net




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA12A234-A3D1-4EC1-8BA1-49E646A356E9>