Re: Booting anything after r352057 kills console

From: Thomas Laus <lausts_at_acm.org>
Date: Tue, 24 Sep 2019 17:41:33 -0400
> Ian Lepore [ian_at_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
Received on Tue Sep 24 2019 - 19:41:39 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC