On 11/20/17 18:46, Warner Losh wrote: > > > On Mon, Nov 20, 2017 at 4:31 PM, Thomas Laus <lau...@acm.org > <mailto:lau...@acm.org>> wrote: > > Warner Losh [i...@bsdimp.com <mailto:i...@bsdimp.com>] wrote: > > > > Can you revert this part of the change? Go back to a known-working > version > > of those files? Let me know if that fixes the problem? Bonus points for > > bisecting which one of the few dozen commits I did that caused this > > regression... > > > > I don't have a GELI + ZFS test bed here. > > > I have another PC that is operational and is running CURRENT last > built about a week ago. I'll copy it's gptzfsboot file to a memory > stick and try loading it on the non-functioning PC in the morning. > I'll let you know how it comes out. > > > Please do. I fear I screwed something up in the massive rototilling I > did, despite efforts to the contrary, and any help you can give me > tracking it down would be greatly appreciated. > I had boot success when copying gptzfsboot file from my laptop that is running r325474. The problem CURRENT version running on my desktop is r326012. The UPDATING note describing the latest changes just has a date of 201711xx. How far back should I go to start the isolation process?
Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF _______________________________________________ email@example.com mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"