From owner-freebsd-current@FreeBSD.ORG Wed Apr 8 17:52:08 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95D4B811 for ; Wed, 8 Apr 2015 17:52:08 +0000 (UTC) Received: from shxd.cx (mail.shxd.cx [64.201.244.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7772DF23 for ; Wed, 8 Apr 2015 17:52:08 +0000 (UTC) Received: from 50-196-156-133-static.hfc.comcastbusiness.net ([50.196.156.133]:31468 helo=tinkerbell.pixel8networks.com) by shxd.cx with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1YfsBh-0006zf-2n; Wed, 08 Apr 2015 08:46:45 -0700 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: Nothing can boot anymore - video issues From: Devin Teske In-Reply-To: <1428506302.5499.10.camel@hardenedbsd.org> Date: Wed, 8 Apr 2015 10:51:58 -0700 Message-Id: References: <369848B3-73AB-4A71-9597-9ED098C7EF64@me.com> <1428343182.6806.3.camel@hardenedbsd.org> <1428352517.6806.10.camel@hardenedbsd.org> <6D9FB562-9899-4180-A07A-232EEE2A09DB@FreeBSD.org> <1428506302.5499.10.camel@hardenedbsd.org> To: Shawn Webb X-Mailer: Apple Mail (2.1990.1) Sender: devin@shxd.cx Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current@freebsd.org, Devin Teske , Rui Paulo X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Apr 2015 17:52:08 -0000 > On Apr 8, 2015, at 8:18 AM, Shawn Webb = wrote: >=20 > On Mon, 2015-04-06 at 16:55 -0700, Devin Teske wrote: >>=20 >>> On Apr 6, 2015, at 1:35 PM, Shawn Webb >>> wrote: >>>=20 >>> On Mon, 2015-04-06 at 13:59 -0400, Shawn Webb wrote: >>>> On Sun, 2015-04-05 at 12:07 -0700, Rui Paulo wrote: >>>>> On Apr 5, 2015, at 09:11, Shawn Webb >>>>> wrote: >>>>>>=20 >>>>>> So I just updated my laptop and desktop to a recent HEAD. Both >>>>>> machines >>>>>> boot using gptzfsboot. The boot spinner shows, then when it's >>>>>> supposed to >>>>>> transition to the Beastie logo screen, the monitor funks out. >>>>>> Booting never >>>>>> finishes. Below is a link to a picture of my laptop. >>>>>>=20 >>>>>> http://imgur.com/l3mLDBX >>>>>=20 >>>>> Try reverting the Forth changes. That's all that comes to mind. >>>>>=20 >>>>> -- >>>>> Rui Paulo >>>>=20 >>>> I'm going through commit-by-commit from April 3rd to March 31st, >>>> which >>>> will take a big chunk of time. It's really weird that no one else >>>> has >>>> reported this since even my VirtualBox VMs have this same issue. >>>>=20 >>>> Thanks, >>>>=20 >>>> Shawn >>>=20 >>> I've figured out the commit that caused the breakage. Looks like the >>> boot Forth changes are pretty bad. The commit that caused the >>> breakage, >>> as far as I can tell is, r280974. Reverting that and the two commits >>> above that revision regarding sys/boot/forth allowed me to boot >>> again. >>>=20 >>> Now the boot screen looks like this: http://imgur.com/I9SVHfT >>>=20 >>> I can now boot, but as you see, the boot screen's messed up. >>>=20 >>>=20 >>=20 >>=20 >> Why the screen looks that way (no brand and no logo): >> You were caught in a small window of broken-ness. >>=20 >>=20 >> Window was between: >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D280933 >> and >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D281002 >>=20 >>=20 >> A window of approximately 2 days. >>=20 >>=20 >> As for why the screen got wonky =E2=80=A6 well=E2=80=A6 your comp and = my >> comp don=E2=80=99t agree on ANSI sequences. I=E2=80=99ve reverted the = offending >> changes so that we may once-again agree on ANSI codes. ;D >=20 > It now appears that the problem was specific to HardenedBSD: we had a > custom loader_version setting in sys/boot/forth/loader.conf. I'm = unsure > which commit caused the breakage, but now having a custom = loader_version > will break booting. >=20 Thanks for narrowing it further. Let me do some additional testing and I=E2=80=99ll report back what I find. =E2=80=94=20 Devin=