Date: Wed, 25 Sep 2019 17:51:44 -0400 From: Thomas Laus <lausts@acm.org> To: Ian Lepore <ian@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Booting anything after r352057 kills console Message-ID: <8a093bb0-3167-ab89-f9d5-d938fc3d9d95@acm.org> In-Reply-To: <9ce93cb3283ee900eb63393f7bdb747001743cad.camel@freebsd.org> References: <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org> <18332.1569268545@critter.freebsd.dk> <20190923213222.GA57158@mail.laus.org> <0eb339eb-5eb2-b75b-7fef-c22d02b824af@nomadlogic.org> <93d9c5bf-8269-ba44-655e-f079b311e29c@acm.org> <06a455da-1c7a-84f3-f4e4-64b50ca769bb@nomadlogic.org> <a377f6d1-840f-57d7-f410-d30b4397a699@acm.org> <9ce93cb3283ee900eb63393f7bdb747001743cad.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-09-24 15:09, Ian Lepore wrote: > > On my system, a whole lotta stuff happens between ntpd and syscons (the > thing that configures blanktime). Try setting rc_debug=YES in rc.conf, > that should write more info to syslog about what's happening between > ntpd and the lockup point. > Ian: I was able to mount my zfs filesystem r+w and added the rc_debug="YES" to my rc.conf. The additional debug messages were written to the beadm boot environment /var/log/messages. Since the computer locked up, I was unable to read this log and email the results. That log is inaccessible to a running beadm snapshot, so I gave up on this quest. I blew away my source and object files and did a fresh checkout of HEAD today. Everything built fine and I was able to boot r352710 today. Thank you and the rest of this list for the help along the way. I guess that this is just one of those computer mysteries that won't get solved at thus time. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8a093bb0-3167-ab89-f9d5-d938fc3d9d95>