From owner-freebsd-arm@freebsd.org Wed Nov 8 20:18:49 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FE4CE5B289 for ; Wed, 8 Nov 2017 20:18:49 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-141.reflexion.net [208.70.210.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5F18661E9 for ; Wed, 8 Nov 2017 20:18:48 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18499 invoked from network); 8 Nov 2017 20:18:41 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 8 Nov 2017 20:18:41 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Wed, 08 Nov 2017 15:18:41 -0500 (EST) Received: (qmail 9904 invoked from network); 8 Nov 2017 20:18:41 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 8 Nov 2017 20:18:41 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id D1AF3EC9553; Wed, 8 Nov 2017 12:18:40 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: RPi3 boot failure with r325156 snapshot Date: Wed, 8 Nov 2017 12:18:40 -0800 References: <1510012249.2152828.1163794192.4049F0E8@webmail.messagingengine.com> <20171107091135.GA37713@jodi.ci.com.au> To: Richard Perini , Hyun Hwang , freebsd-arm In-Reply-To: <20171107091135.GA37713@jodi.ci.com.au> Message-Id: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2017 20:18:49 -0000 On 2017-Nov-7, at 1:11 AM, Richard Perini 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