From owner-freebsd-arm@freebsd.org Thu Nov 30 00:54:26 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 9E152DEF32A for ; Thu, 30 Nov 2017 00:54:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 609146C526 for ; Thu, 30 Nov 2017 00:54:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id d14so5731180ioc.5 for ; Wed, 29 Nov 2017 16:54:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=QLMSAF9nLX8GKcendxGFBkU4afXy2lfIuGl7C8y9lFw=; b=txKGW12oR5WZ4K7hzBzsn3F9Jluy+KQAh/IV162hn3kt9Kph+EPbrBSpBSnsOKrLrK xoknvJOwg10lBWkHw2vdxYD4WkMp9AkVPx6zQcQp+N36Hksm+nctZVGoZjyQOBMTIwuP PxWmzNGAC5y0nGM5qPdaoGDbc/nPVWZy4UuajiuuzHkQWgQYwVLfxph0AOLBSNxlYVLo bt/mLfrp14gCeZC4mPlDI1Zsl0SiYlVVj836Z/Tx5PJh0pAAT6bI4donMMwfwx2rEcHn 1yOlvFrrbTeIAUGZLtOJoijmnK6Kyw4XBpnZgK6ceC1h1o2Op+s5k2EhA3UaJz2ojXa2 CCkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=QLMSAF9nLX8GKcendxGFBkU4afXy2lfIuGl7C8y9lFw=; b=OXZOQGRMDOqDjV5OydPbtnh163WCKFkQ27YgjaYFz1M1u2pJTzh18ZLi7o9KvgAq3H ieGB1RAd3bqUFhr59ZaCo3+9uaf2nfECmRUje9YVBhOs3UjnXoYY5VSsqES3t/z5646P ORcmUdJ0ix5aNk/YBhtptzPDX8b0hdVbTGG9Rs5QAzWhXu8/s82xGDkFjgRGLLjTLEgq Dwxel13sHFQfT6kbgch3waO7aE4ieJsO5kWq8zUvxR26AJCfTmpTE9qgtb8vxt1F3zk9 hvdInafz7CxcI/LCWrPHQzS/wGMrYFfWDrRStNvPdOIJukTyD5ujm32HZtBJju3NjtV0 +ObA== X-Gm-Message-State: AJaThX5fldFM0r+NoQCUtaRl6JB/K+k6aSE9/sGd3DQehA90zD8MPiLU jRsrNadVoFMpJY6lF5KFEKPQ/1uKfc8jPoyweBo8IA== X-Google-Smtp-Source: AGs4zMb1mrLE8yhDuyCEp5pRjH3Q09rau7iJjxeHFN2zqnxeOTQI8UEEQkpYdRrnD069lOxM70l2Z3olR93GmHI4+uA= X-Received: by 10.107.104.18 with SMTP id d18mr5311566ioc.136.1512003265699; Wed, 29 Nov 2017 16:54:25 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Wed, 29 Nov 2017 16:54:25 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171130004358.usia2jrvman4cvvz@mutt-hbsd> References: <20171130002135.q7p27hh6qkog4slr@mutt-hbsd> <20171130003458.bnltotlgfdbke5ue@mutt-hbsd> <20171130004358.usia2jrvman4cvvz@mutt-hbsd> From: Warner Losh Date: Wed, 29 Nov 2017 17:54:25 -0700 X-Google-Sender-Auth: bndQhTjws8JqDaHqpehAC7sQyHs Message-ID: Subject: Re: Booting UEFI ZFS is broken on arm64 To: Shawn Webb Cc: "freebsd-arm@freebsd.org" , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 00:54:26 -0000 On Wed, Nov 29, 2017 at 5:43 PM, Shawn Webb 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 > > 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.webb@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