On Wed, Nov 29, 2017 at 5:43 PM, Shawn Webb <shawn.w...@hardenedbsd.org> wrote:
> On Wed, Nov 29, 2017 at 05:42:52PM -0700, Warner Losh wrote: > > On Wed, Nov 29, 2017 at 5:34 PM, Shawn Webb <shawn.w...@hardenedbsd.org> > > wrote: > > > > > On Wed, Nov 29, 2017 at 05:33:46PM -0700, Warner Losh wrote: > > > > On Wed, Nov 29, 2017 at 5:21 PM, Shawn Webb < > shawn.w...@hardenedbsd.org> > > > > wrote: > > > > > > > > > It appears that in the latest FreeBSD 12-CURRENT/arm64 snapshot, > > > > > booting UEFI GPT ZFS on my OverDrive 1000 is broken. It boots up to > > > > > this line: > > > > > > > > > > Using DTB provided by EFI at 0x801fe00000. > > > > > > > > > > > > Which snapshot is that? Boot1 was broken until recently. > > > > > > FreeBSD-12.0-CURRENT-arm64-aarch64-20171121-r326056-memstick.img > > > > > > It also happens on latest HEAD, so it would appear to still be broken. > > > > > > Is this boot1.efi producing the output, or loader.efi? I'm guessing the > > latter, but wanted to make sure. If so, then we're past the point where > > boot1.efi would have failed (besides, it was fixed before that snapshot). > > With DEBUG turned on for stand/fdt: > > Booting [/boot/kernel/kernel]... > fdt_copy(): fdt_copy va 0x01208000 > fdt_setup_fdtp(): fdt_setup_fdtp() > fdt_load_dtb_addr(): fdt_load_dtb_addr(0x801fe00000) > Using DTB provided by EFI at 0x801fe00000. > Loaded the platform dtb: 0x81f56f1630. > fdt_fixup(): fdt_fixup() > > ^ hangs after that message That doesn't sound like anything I've changed, but it could well be... I think to find this breakage, you may need to bisect backwards along stand / sys/boot until we find the spot where it broke. Warner _______________________________________________ firstname.lastname@example.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"