Date: Wed, 6 Dec 2017 12:48:29 -0500 From: Thomas Laus <lausts@acm.org> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171206174829.GA1204@mail.laus.org> In-Reply-To: <CANCZdfp0AS-=xD8KvqgPkpFnM_7-Gc=CmLiHE9T=qo0_d1zYwg@mail.gmail.com> References: <d92d0e84-72c5-e240-a1b5-18cef53dcbff@acm.org> <CANCZdfqHZidf%2BZvf3Pqpr1BHuyRPBP9zLSzkw_CcFqJde2KzYw@mail.gmail.com> <20171206164801.GA1055@mail.laus.org> <CANCZdfp0AS-=xD8KvqgPkpFnM_7-Gc=CmLiHE9T=qo0_d1zYwg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh [imp@bsdimp.com] wrote: > I've been *VERY* busy between then and now cleaning up the boot loader > "accumulated technical debt". Alas, sounds like I've broken something. So I > think it's a binary search: I'd start with 326370 as the pivot and 326500 / > 326250 as the next steps if it succeeds / fails. > > So you are seeing a BTX error? Before we even get to running /boot/loader, > correct? Any chance you can get me that error? > I get a screen full of register and hex numbers followed by BTX halted. I can do my best to transcribe all of the numbers, but that may be very error prone to do by hand. At this point in the boot process, it is a little hard to fire up a serial console and capture the output to a file. I run Geli encrypted disks and the BTX halt comes even before the prompt for a password. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171206174829.GA1204>