From owner-freebsd-current@freebsd.org Wed Dec 6 17:28:22 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 98ED3E85FB8 for ; Wed, 6 Dec 2017 17:28:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 58E727A813 for ; Wed, 6 Dec 2017 17:28:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id r6so7987729itr.3 for ; Wed, 06 Dec 2017 09:28:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=UK40P0gYSap52KjOM2ZIk8GyfArviPIttQD6Uz98G/Y=; b=qgpjbuVpjhEVqv4sT5YikrSKgkB0glo1SEn21Y7/KYea5cdaKcnqS0IcIKam0cKJe5 AtB5IxvEdo41BdYUqr91v4MntxnvbYHVREmS73rFH85h9hMuhfgKJYmTJ0t9XaorRmBL IpyuEXoFK5OThYmGqC2VGLtGHIMGTxra2GGcVKbQvMr0gkIN0B8jHg22zi1ub6+w2fvc 9QIGXvXnZDXqDNKSNpRzIKI/1AF9PUcbbRROGFWFNHAc++DTcPtcbW7lMV6+NWzyVKnf +YyJzEIm0CM8iCNZL+bQaGZ/SMir+m6dfKh0vXGEhKyfHQnUMP1xPROIRjX1lXbj64xj v9Xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=UK40P0gYSap52KjOM2ZIk8GyfArviPIttQD6Uz98G/Y=; b=CjOuiLeQC0RJRPqWD6zCTALHlKLA1OGvvxxLTd1cfeZ7JB/FJSmwmDQqjyIewyW47d oRdhCyobMrxU8+MvhyIoBV2hZLaArOcN9dr0w7V2PKURN0/sLD5s7/MMM+5a1KB/+Leq oOaEKSWaDom+26xJHIAfiJVi4brq9P5Q3f8ASIXmlGlBroc19XI0Z+AbmGoc9vcLBSG/ b8AQ8xEPMxM0E6MMgrrMGVR+Eu5b4HvEy9AWWmnredgVfNyCWoUV+sBtIDJqF9L6Ajky rYomyQR/6GwjgJ5/2VsSzmGYz6l7YrjFFPiC0vMxp1CZiUpKLKMses3u2KvZvuv3MrhE hcIg== X-Gm-Message-State: AKGB3mIm1V0Zyux0aZRj6lN2l7/erwYwO8hJr5HXXvflCaL3//q+rMqi itqdpANSe0MnnNxjSq8oVf6fs2+uC2b3CPZMkFbelA== X-Google-Smtp-Source: AGs4zMb/n4C+U1LJrx4qFy4XRyIHX1J6oU9EUDIodYenmSnbDGIyW+4AXSABjIUTAhPe251ETCQLuafXvc4TA45CxTI= X-Received: by 10.36.147.193 with SMTP id y184mr13967520itd.64.1512581301260; Wed, 06 Dec 2017 09:28:21 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Wed, 6 Dec 2017 09:28:20 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171206164801.GA1055@mail.laus.org> References: <20171206164801.GA1055@mail.laus.org> From: Warner Losh Date: Wed, 6 Dec 2017 10:28:20 -0700 X-Google-Sender-Auth: jzLzcaTC_KW-I-Jj4swtYhYB1vA Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 06 Dec 2017 17:28:22 -0000 On Wed, Dec 6, 2017 at 9:48 AM, Thomas Laus wrote: > 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'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 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. Good! One less problem for me to track... Warner