On Thu, Sep 23, 2021 at 09:20:51PM +0200, Johan Hendriks wrote: > > On 23/09/2021 19:52, Konstantin Belousov wrote: > > On Fri, Sep 24, 2021 at 12:43:01AM +0900, Tomoaki AOKI wrote: > > > On Wed, 22 Sep 2021 23:09:05 +0900 > > > Tomoaki AOKI <junch...@dec.sakura.ne.jp> wrote: > > > > > > > On Wed, 22 Sep 2021 05:47:46 -0700 > > > > David Wolfskill <da...@catwhisker.org> wrote: > > > > > > > > > On Wed, Sep 22, 2021 at 02:39:37PM +0200, Johan Hendriks wrote: > > > > > > I did a git pull this morning and it fails to boot. > > > > > > I hangs at Setting hostid : 0x917bf354 > > > > > > > > > > > > This is a vm running on vmware. > > > > > > If i boot the old kernel from yesterday it boots normally. > > > > > > > > > > > > uname -a > > > > > > FreeBSD varnish-cdn-node03 14.0-CURRENT FreeBSD 14.0-CURRENT #0 > > > > > > main-n249518-5572fda3a2f: Tue Sep 21 14:40:22 CEST 2021 > > > > > > root@varnish-cdn-node03:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64 > > > > > > .... > > > > > I had no issues with my build machine or either of two laptops, either > > > > > from yesterday: > > > > > > > > > > FreeBSD g1-55.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #358 > > > > > main-n249518-5572fda3a2f3: Tue Sep 21 05:15:22 PDT 2021 > > > > > r...@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > > > amd64 1400033 1400033 > > > > > > > > > > or today: > > > > > > > > > > FreeBSD g1-55.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #359 > > > > > main-n249556-c96da1994587: Wed Sep 22 04:24:17 PDT 2021 > > > > > r...@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > > > amd64 1400033 1400033 > > > > > > > > > > [uname strings from my main laptop shown, but I keep the machines > > > > > in sync rather aggressively.] > > > > > > > > > > Perhaps the issue you are encountering involves things not in my > > > > > environment (such as VMs or ZFS)? > > > > > > > > > > Peace, > > > > > david > > > > > -- > > > > > David H. Wolfskill da...@catwhisker.org > > > > > Life is not intended to be a zero-sum game. > > > > > > > > > > See https://www.catwhisker.org/~david/publickey.gpg for my public key. > > > > For me, on bare metal (non-vm) amd64 with root-on-ZFS, > > > > > > > > Fails to boot to multiuser at git: 8db1669959ce > > > > Boot fine at git: 0b79a76f8487 > > > > > > > > Boot to singleuser is fine even with failed revision. > > > > > > > > Failure mode: > > > > Hard hangup or spinning and non-operable. Hard power-off needed. > > > > Seems to happen after starting rc.conf processing and before setting > > > > hostid. > > > > > > > > -- > > > > Tomoaki AOKI <junch...@dec.sakura.ne.jp> > > > > > > > Additional info and correction. > > > *Hung up before setting hostuuid, not hostid. > > > > > > *^T doesn't respond at all, only hard power off worked. > > > > > > *`kldload nvidia-modeset.ko` on single user mode sanely work. > > > > > > > > > Why I could know rc.conf is started to be processed: > > > > > > I have lines below at the end of /etc/rc.conf and its output is always > > > the first line related to /etc/rc.conf, at least for non-verbose boot. > > > The next line is normally "Setting hostuuid: " line, which was not > > > displayed when boot hung up. > > > > > > > > > kldstat -q -n nvidia.ko > > > if [ 0 -ne $? ] ; then > > > echo "Loading nvidia-driver modules via rc.conf." > > > if [ -e /boot/modules/nvidia-modeset.ko ] ; then > > > kld_list="${kld_list} nvidia-modeset.ko" > > > else > > > kld_list="${kld_list} nvidia.ko" > > > fi > > > fi > > If you do not load nvidia-modeset.ko at all, does the boot proceed? > > > > When the boot hangs, can you enter into ddb? > > > > > I do not load a nvidia-modeset.ko kernel module and it will not boot. It > hangs with Setting hostid : as the last message. Then only a powercycle gets > me back. If i boot in single user mode all is fine, but as soon as i exit > single user mode it hangs at the same spot.
Can you enter ddb at the hang point? Do you load any other modules besides nvidia, from rc.conf?
