From owner-freebsd-current@freebsd.org Mon Apr 29 15:14:43 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD83A1593BDE for ; Mon, 29 Apr 2019 15:14:42 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DE044882B9 for ; Mon, 29 Apr 2019 15:14:41 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1556550880; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=R3dIE8sbMiuZC9oWqS/hVcHPor5bIy1b14RdP3G1+fD/JVnyHXXd1DAPPwKGZrYD+626H4z2RxYCw GOmc6iDFTYWvg1yHTz81M9C+BKsZ91HEYOb6nQdDdWRqVIVcCo8ZrucEKxHEQpB85V23p2HPlaLI1D o1jO3N81wmpHE7gdgo+F5r2+aQJTc5QxkONEFOE6cy0Zni/ajI2CmA7EA7z/UEyylB7TS1dvvgmrmd GDzc7Hd/kuaTTwM0CQUYARUX4dHawAhvMjl7WXfsIEen9/Nbrb4wEMZSk60a+089WZrTv25APFVWV1 oZTUfjnPhCqqId8wF2cyd6SoIN8ci/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=BCDzZmU8QJs1NjC+9olTAWCo3Q4GDOo/e3Os7zMc/ao=; b=j6C3Zf0OFFIp9+rDgOQIuIFRly8fslK+RUvmNj+1zzgtZJ2UqVXRJwPibaCZcZnR8RKKqvI0gCJiF zMett5b1OORkrUDQ2u3gZDnThfnHrNoE9Pe4XrUFqH7Wv14qGMBRJnpUxoy98UlEUNmAn1p/bfwqEQ pHqnFka2eArkAVuG+U94aSbVbvsRsMn+7Ep+rWmxj6vDk4lKc0B32rmpyLqgOHUpFrxvgO8i1ToSes 0gSz1aR9OBJtLvHTt9xNDsCYnB+Ud183EZ6xGTz4yig/IzAEGLas91A/7LIfPErr2QVRPa+Yhh42rj wKz7F2dE74Ks1N11iVenCGTbK9n/tTw== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=BCDzZmU8QJs1NjC+9olTAWCo3Q4GDOo/e3Os7zMc/ao=; b=UrQZE5hr6XQ+Y57ix5BOvqqAA+dPl/A+IyLY/+CN4gZLQ0q/ACe2o5qcBS43A7/NNnoE36SJv1Ols Zptg8dakS6foc2eLwlxi9OG77tDY33EpTWKLj9mMTYaXZUStrbIXjrLjJsOc7LDdTePFsLkB3KV96Q xQTWaCqb9MJcBqQHTnenpBHr2tFdyu0HLhG18d0Z6Wm+POp0OT+VZBM8Ms7zGvLghTaRiL2wGOx883 xguFA0Agd+qsUnALPZL5dD3Esjsi0WEKaO3gsyEQ+b8GLVAlhJEiU0POKbw3UB7/yAprUMh8Cp6CCd uToj23O2DN7qUjymbNmwZrK3M2eHuqQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: 81321ccc-6a91-11e9-990e-673a89bc4518 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 81321ccc-6a91-11e9-990e-673a89bc4518; Mon, 29 Apr 2019 15:14:39 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x3TFEcHh003352; Mon, 29 Apr 2019 09:14:38 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <0848043e68641ea47b918b8480ac8a5a3bb773e0.camel@freebsd.org> Subject: Re: Question about 'gptzfsboot' From: Ian Lepore To: lausts@acm.org, FreeBSD Current Date: Mon, 29 Apr 2019 09:14:37 -0600 In-Reply-To: <5bf88341-80f0-3aff-f51a-0b1975530f2e@acm.org> References: <01d10a11-49b2-2982-01cb-b49a0831d30b@acm.org> <5de29e0b5228d7eb0aac8e0eec116896f11ea862.camel@freebsd.org> <5bf88341-80f0-3aff-f51a-0b1975530f2e@acm.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: DE044882B9 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-1.00)[-0.995,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 29 Apr 2019 15:14:43 -0000 On Mon, 2019-04-29 at 10:33 -0400, Thomas Laus wrote: > > On 2019-04-28 22:27, Ian Lepore wrote: > > > > > > If you're using gptzfsboot, I guess you're using zfs? I just > > > fixed a > > > problem with probing disks for zfs volumes a few days ago > > > (r346675). > > > There is even some small chance it fixes this problem, because > > > one of > > > the things I noticed was that in one of the disk structures in > > > loader, > > > the "slice offset" value was sometimes a bit random-looking, like > > > it > > > was being initialized with whatever garbage was laying around in > > > memory. It actually makes some sense that the "garbage" might be > > > different between a firstboot after power-on and a reboot. > > > > > > So all in all, it wouldn't hurt to update both gptzfsboot and > > > loader > > > (gpart bootcode -b and -p) to see if there's a fix lurking in my > > > zfs > > > probe changes. > > > > > > > I'll build and update my laptop OS this morning and report back to > > this > > thread if I have any additional issues. > > > > Ian: > > Updating to r346885 turned out to be a disaster! There were changes > to > DRM between FreeBSD 13.0-CURRENT r346544 and r346885. The desktop > that > I use for a build machine because it is much faster than any of my > other > PC's installed kernel and world without any problems including > starting > 'X'. I had to update the drm-current-kmod port on my build > PC. Nothing > was in /usr/src/UPDATING or /usr/ports/UPDATING about the need to do > so. > DRM on my build computer did not start until the update and then > worked > as expected. > > I did the same on my Dell laptop and it crashed on the first boot > right > after loading DRM-kmod. I removed the line in rc.conf that activates > the kernel module and my laptop booted into multiuser. When I > started > 'X' it crashed just like before. The screen was black and I could > not > login remotely via SSH. Nothing in any system log. The Xorg log > shows > this and stops: > > 40.979] compiled for 1.18.4, module version = 2.4.0 > [ 40.979] Module class: X.Org Video Driver > [ 40.979] ABI class: X.Org Video Driver, version 20.0 > [ 40.979] (II) intel: Driver for Intel(R) Integrated Graphics > Chipsets: > i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, > 865G, > 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, > Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, > Q35, > Q33, > GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 > [ 40.981] (II) intel: Driver for Intel(R) HD Graphics > [ 40.981] (II) intel: Driver for Intel(R) Iris(TM) Graphics > [ 40.981] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics > [ 40.981] (II) modesetting: Driver for Modesetting Kernel Drivers: > kms > [ 40.981] (II) scfb: driver for wsdisplay framebuffer: scfb > [ 40.981] (II) VESA: driver for VESA chipsets: vesa > [ 40.981] (--) Using syscons driver with X support (version 2.0) > [ 40.981] (--) using VT number 9 > > I had to recover my system using beadm to rollback to the last > CURRENT > snapshot from a week ago. > > Tom > > I'm fighting my own video driver troubles (seems like a lot of that going around lately); on an upgrade of a machine from 11-stable to 12- stable I lost my console. But, a broken kernel and/or userland shouldn't affect your ability to use the new boot components. That is, you can use gptzfsboot and loader that contain my fixes, and use them to load an older kernel that has working video drivers. -- Ian