Date: Mon, 18 Dec 2017 17:52:41 +0100 From: "O. Hartmann" <ohartmann@walstatt.org> To: Warner Losh <imp@bsdimp.com> Cc: "O. Hartmann" <ohartmann@walstatt.org>, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>, antranigv <antranig@vartanian.am>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: r326820 stuck on bootloader Message-ID: <20171218175308.139afde8@thor.intern.walstatt.dynvpn.de> In-Reply-To: <CANCZdfpD=u-ZuzRW%2BqKaOoLxMQ-=XfOO7SKAx1coZsa7nL%2BjNA@mail.gmail.com> References: <9038c936-17db-1405-4d1b-5995ddabfa33@vartanian.am> <201712181335.vBIDZXNb016145@pdx.rh.CN85.dnsmgr.net> <20171218171647.384ae7f2@thor.intern.walstatt.dynvpn.de> <CANCZdfpD=u-ZuzRW%2BqKaOoLxMQ-=XfOO7SKAx1coZsa7nL%2BjNA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <imp@bsdimp.com> schrieb: > On Mon, Dec 18, 2017 at 9:16 AM, O. Hartmann <ohartmann@walstatt.org> wro= te: >=20 > > Am Mon, 18 Dec 2017 05:35:33 -0800 (PST) > > "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171218175308.139afde8>