From owner-freebsd-current@freebsd.org Mon Dec 18 16:53:30 2017 Return-Path: Delivered-To: freebsd-current@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 B985AE9A7A1 for ; Mon, 18 Dec 2017 16:53:30 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 39EFF63529 for ; Mon, 18 Dec 2017 16:53:29 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.187.99]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MSMw7-1eb3WI261b-00TWoO; Mon, 18 Dec 2017 17:53:17 +0100 Date: Mon, 18 Dec 2017 17:52:41 +0100 From: "O. Hartmann" To: Warner Losh Cc: "O. Hartmann" , "Rodney W. Grimes" , antranigv , FreeBSD Current Subject: Re: r326820 stuck on bootloader Message-ID: <20171218175308.139afde8@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <9038c936-17db-1405-4d1b-5995ddabfa33@vartanian.am> <201712181335.vBIDZXNb016145@pdx.rh.CN85.dnsmgr.net> <20171218171647.384ae7f2@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/ao1i4xago9Uh.o4iVPJILBN"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:fnmXz80m6HznJjnRoRU4IOSbHOfWtbPyPJhREL4Ka7U8QtooJFj fVOc9iwBxjFcs9QH7BLrwmmqUB7nL6hrt1H2BR0GMoUH7qMU2d2keDMXyZ+OydQe4Yh60b0 WWfFjhvAVwB1CX1G+vjCcFaFKDTrRMq6oL0qoFQaRQLzTf9hxasyZqH0CHyVZpm8f8b4DL2 j6WaX0OPcBMZH7Q7XHJrg== X-UI-Out-Filterresults: notjunk:1;V01:K0:pOKwV/3HYqo=:Dm+djG1UA4kpH7A5oS9SsW xUPxXmWy0ROA+OgKcQjW8ov25FNctwZKB8MX4xD3bitXmAEKW/5N+HrkdESHt/oM6v0fyHWo2 Oxdd/9NAXbanRZQOLhCuAYlIcH+L4nWGz52lwWL2pB+c28OCTjrlOJzn+rQri/pE3TcFzhQWN nkFdyNS9+ISxYAD6h1VWSXW3kPiZOn0CKvo4TYJetu8ynAsCerumiVaa9AOrPJdlSr4cHPP5L yc/X88/GBjVZaa+MquPbVGHEuFSVVYiQHfJyf34EaqpfjOVILQPtAzuoUeq7fUh2brvy0anSS l6/9JNjHUz9IcmyxzEWLMUeJIkNGx7qrn/SO1KcdgXJdrqcsE0HMaZYNQomWctpT+bumeM5ak SsDv5kYfwRxzNRZ7vDe34Fi3CfGG5pLtdE3Sdw32x3JgESL21i1AmkrW1iSFXpWvnpMLk+wNJ dcISUDOTnTE4LPZDaAc3pV0/7kdKVhbhIfM+16Ykhn+k4Vj2wd15PaGIs3a7+3bOdM51NMoGW bNpMEIyS9He383lcE5uxZFAgHa7xs7F8WQsPRoTWfzl/kw7zvCNRWieRwQTilv8GxzCzDY2KW gdADZTwu1a7SIMTzHnI2YXtLipQs+yS6OSe0eLEbha4oT/r/ZG4ta8l/2f9+TTnnefq3CPVwN fwEE+14LVC75pFxGKvXldFTPOIL+/DiCdDaTSrREVfq7mNq7EYwaCTv7vU/VFkG3SP7RjKvh4 AXSwtZeIMhzsrGIcKUod4DMD/2MSMscFiC+Mt8XS0CpKX6N2yGu4IfFWZQL6sKNCE38T9QP1G EVTm6dxAoYQoXc/y/DK03JSape9jw== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 16:53:30 -0000 --Sig_/ao1i4xago9Uh.o4iVPJILBN Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 18 Dec 2017 09:48:01 -0700 Warner Losh schrieb: > On Mon, Dec 18, 2017 at 9:16 AM, O. Hartmann wro= te: >=20 > > Am Mon, 18 Dec 2017 05:35:33 -0800 (PST) > > "Rodney W. Grimes" schrieb: > > =20 > > > =20 > > > > Hey all! > > > > > > > > I have just downloaded > > > > FreeBSD-12.0-CURRENT-amd64-20171213-r326820-memstick.img.xz and > > > > decompressed it, trying to boot it on QEMU and I get "Consoles: > > > > internal video/keyboard" and then it's stuck. > > > > > > > > I actually have no idea how to debug, any help would be appreciated= . =20 > > > > > > This snapshot may have broken boot code in it, I had problems > > > installing it to a zfs system and had to post install replace > > > my zfs boot blocks from those of 20171206. > > > > > > =20 > > > > Thanks in advance, > > > > - -- > > > > antranigv =20 > > > =20 > > > > The shit hit the fan at > r326593 (this is what Warner wrote me back, I > > had no problems > > with r326583, but r326584 and beyond had compilation issues). I tried > > r326593 and it > > worked for me (had issues on a serial console for the PCengine APU2C4). > > > > From usr/src/UPDATING, tag designated by "20171215": > > > > 20171215: > > r326887 fixes the issue described in the 20171214 UPDATING entr= y. > > r326888 flips the switch back to building GELI support always. > > > > [...] > > > > I tried the first time r326888 on the APU 2C4 and it worked again - this > > doesn't imply > > that the GPT GELI and ZFSBOOT loader are all right again, but Warner Lo= sh > > stated it is > > fixed. > > =20 >=20 > Yes. I've confirmed that zfsboot works with or without the GELI code > compiled in. I've not confirmed that ZFS + GELI partitions work. I haven't > updated my test scripts in tools/boot/genroot.sh to create them yet. If > someone who knows this stuff really well wants to do that for one image > (gpt + zfs + geli) I can (a) test and (b) generalize. >=20 > Warner Oh, my bad. So it is still to use with caution? At that point I can not understand why the build of bootable images is stil= l in progress. People which desperate in need of a bootable image may download the wrong o= ne from the FreeBSD site - and find out the harsh way it is broken. If the build of tho= se images is automated - can this be stopped? --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/ao1i4xago9Uh.o4iVPJILBN Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWjfydQAKCRDS528fyFhY lMAUAf9wP4TjnV1ibKv1eIXSQKcx+rp5b1leqF8WEXnvI+0Pc/Exv9mxAhHwMHe3 gc8G6KOYTGY6Io91AUSxIKjJ+zWPAgCEz+V7yaDzVWuTgJI2uwb0f5CVcB/+k8OY A8RMeGYlk8ymU0k39tdnuUytCn2CP1GfeGQR79wBLH+sUUZkgEQI =/40Q -----END PGP SIGNATURE----- --Sig_/ao1i4xago9Uh.o4iVPJILBN--