Date: Tue, 24 Sep 2019 17:41:33 -0400 From: Thomas Laus <lausts@acm.org> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Booting anything after r352057 kills console Message-ID: <20190924214133.GA61889@mail.laus.org> In-Reply-To: <20190924205706.GA61788@mail.laus.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> <20190924205706.GA61788@mail.laus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Ian Lepore [ian@freebsd.org] 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. > > > The results were not very informative. The 'bad' release did not show any > additional log entries with the rc_debug turned on. The working release > was very chatty. Maybe this will get closer to finding the root cause? > I just realized that the rc.conf file is part of the BEADM boot environment and when I switch releases, rc.conf comes with it. I will need to grab my ZFS admin book and find out how to mount a zfs filesystem from the loader prompt and remove the 'read only' attribute so that I can edit the rc.conf that will be used to load the 'bad' release. Maybe then I will have something useful to report 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?20190924214133.GA61889>