From owner-freebsd-current@freebsd.org Tue Nov 21 12:48:56 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF9B0DEE0F1 for ; Tue, 21 Nov 2017 12:48:56 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A5B0F6D3F6 for ; Tue, 21 Nov 2017 12:48:55 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id H800esHjG7gT0H802exJEA; Tue, 21 Nov 2017 12:50:02 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vALCmo9P020982 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 21 Nov 2017 07:48:51 -0500 (EST) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] Reply-To: lausts@acm.org Subject: Re: Loader.conf problem To: Warner Losh Cc: FreeBSD Current References: <20171120214220.GA18207@mail.laus.org> <20171120233112.GA18443@mail.laus.org> From: Thomas Laus Message-ID: Date: Tue, 21 Nov 2017 07:48:50 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfPtvLXQOMzyFlokI+AWtL6rZKFFjV80Jy8rmKfYEXLnsrCKMg0sVhkdyiYi/+VFneIOmGGlpsS2uSDOlDBivSAjtxKlAt+cHYVgOQ3knEtQZPAVXa0wF dIYyJdH6eYBrDUvfvo4ol/K/u+TgASrpyCz7sjNSBw4E3rejKOEVwbGsKaXJdXlWrCkffPlQ2Q9G8ZRF7bw1Bb9jqhYWV0TZmoE= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2017 12:48:57 -0000 On 11/20/17 18:46, Warner Losh wrote: > > > On Mon, Nov 20, 2017 at 4:31 PM, Thomas Laus > wrote: > > Warner Losh [imp@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