Date: Wed, 6 Dec 2017 11:48:01 -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: <20171206164801.GA1055@mail.laus.org> In-Reply-To: <CANCZdfqHZidf%2BZvf3Pqpr1BHuyRPBP9zLSzkw_CcFqJde2KzYw@mail.gmail.com> References: <d92d0e84-72c5-e240-a1b5-18cef53dcbff@acm.org> <CANCZdfqHZidf%2BZvf3Pqpr1BHuyRPBP9zLSzkw_CcFqJde2KzYw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh [imp@bsdimp.com] wrote: > > Any chance you can bisect when this happened? I think I'll need more > details to see what happened. What was your old loader that world based on? > My last good gptzfsboot was r326070. I had not built anything since then until this morning when I built world and kernel at r326622. I'll look at the svn history and see where I should start. > > I also see the problem with the loader logs dumping core that others > > have reported recently. > > > > I've not seen these reports, nor do I see if on my loader testing. More > details please? Last I had heard, everything was working... > That was a typo. I had loader on my mind and the core dumps are dealing with logger. I have seen recent messages to this group about logger dumping core and someone is bisecting the issue. I was just reporting that it was still occurring at r326622. 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?20171206164801.GA1055>