Date: Sat, 9 Nov 2019 11:24:49 -0600 From: Kyle Evans <kevans@freebsd.org> To: Chris Ross <cross+freebsd@distal.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Toomas Soome <tsoome@freebsd.org> Subject: Re: UEFI ISO boot not working in 12.1 ? Message-ID: <CACNAnaHvDe6d-YZDy1N8dfUX4cV%2BDj-%2BKq5eP=L=SEaYzVn9PA@mail.gmail.com> In-Reply-To: <20191109164233.GB1053@westeros.distal.com> References: <20191106191711.GK1177@westeros.distal.com> <20191106210256.GL1177@westeros.distal.com> <CANCZdfobLkYeezJQtz38KE%2BTELaiY5M2JfpUy0POzYPdwsGcCA@mail.gmail.com> <1db62ff2-e7df-5bef-7c6d-424f4367370a@freebsd.org> <CAKr6gn0rV8n%2B9g0i9hm0fNYPDx5EcvVFR60QS554M8qFTW9gqg@mail.gmail.com> <24bd3c37-e834-9599-acd9-2f4966916eae@freebsd.org> <CAKr6gn0qeMiKnB_xj-pD4h8gbBWK39Sxh5YS7tTyUfatKww1wQ@mail.gmail.com> <20191107195325.GO1177@westeros.distal.com> <20191109164233.GB1053@westeros.distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 9, 2019 at 10:42 AM Chris Ross <cross+freebsd@distal.com> wrote: > > On Thu, Nov 07, 2019 at 02:53:25PM -0500, Chris Ross wrote: > > > > On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer <julian@freebsd.org> wrote: > > > >> You could try some bisection back along the 12 branch.. > > > > Yeah. I was hoping for an easier path, but. I can try slogging back > > through stable-12 a month or two at a time. > > Okay. I spent a bunch of time moving around stable-12 by date, and > an ISO build from stable-12 as of 2019-10-14 works (rev 353483), and > 2019-10-15 (rev 353541) does not. > > The svn update across that day shows: > > Updating '.': > U stand/efi/boot1/boot1.c > U stand/efi/include/efilib.h > U stand/efi/libefi/devpath.c > U stand/efi/libefi/efinet.c > U stand/efi/libefi/efipart.c > U stand/efi/libefi/libefi.c > U stand/efi/loader/arch/i386/efimd.c > U stand/efi/loader/efi_main.c > U stand/efi/loader/framebuffer.c > U stand/efi/loader/main.c > U stand/libsa/stand.h > U stand/libsa/zalloc.c > U stand/libsa/zalloc_defs.h > U stand/libsa/zalloc_malloc.c > U stand/libsa/zalloc_mem.h > U stand/libsa/zalloc_protos.h > U . > Updated to revision 353541. > > So, there's the commit/commits. Can someone else who knows the intra-branch > process better help me determine where the original change came from, > what it was meant to accomplish, then hopefully we can find out what went > wrong for at least my hardware? > Hi, That helps- thanks! I'm CC'ing tsoome@, as this is basically just r353501 in that range. Can you give the latest -CURRENT snapshot boot as another data point? Thanks, Kyle Evans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaHvDe6d-YZDy1N8dfUX4cV%2BDj-%2BKq5eP=L=SEaYzVn9PA>