Date: Tue, 28 Dec 2021 21:49:23 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260628] FreeBSD 12.3-Release got stuck during the boot process after the update (maybe nsswitch issue?) Message-ID: <bug-260628-227-37yn515jGV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260628-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260628-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260628 --- Comment #5 from Yoshisato Yanagisawa <osho@pcc-software.org> --- (In reply to Graham Perrin from comment #3) Thank you for the information. I did not know freebsd-version command. It should help me to see detailed = step of freebsd-update. Currently, it is like this: $ freebsd-version -kru 12.2-RELEASE-p7 12.2-RELEASE-p7 12.2-RELEASE-p11 I suppose linux_futex, bhybe, and vmci are kernel modules, and that might be why my kernel kept on running with p7. https://bokut.in/freebsd-patch-level-table/#releng/12.2 >From my experience updating FreeBSD without freebsd-update, I suppose freebsd-update updates with this order; kernel first, then userland. I might see it boot fine with kernel and get stuck with userland, but let me see. There seems to be updates in ZFS, but how it relates to this issue? If thi= s is caused by ZFS, I guess I would get stuck in earlier stage like mounting '/', which looks not. (In reply to Remco from comment #4) Thank you for the information, but unfortunately, it might have nothing to = do with this issue because I do not use a virtual machine. It is PRIMERGY TX1310M3. Note that is has Intel(R) PRO/1000 network adapters. Here, I am thinking about the possibility either devd is the cause or not. = For your case, if enabling netif is after devd, I suppose devd is fine but the = step just after devd might be the cause. Then, I should also confirm what comes after devd. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260628-227-37yn515jGV>