Date: Tue, 26 May 2015 08:37:02 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Brandon Wandersee <brandon.wandersee@zoho.com> Cc: Trevor Roydhouse <trev@sentry.org>, freebsd-stable@freebsd.org Subject: Re: Kernel fails to boot after update Message-ID: <alpine.BSF.2.20.1505260834050.26442@wonkity.com> In-Reply-To: <20150525174007.GA6272@WorkBox.Home> References: <20150525025607.GA1071@WorkBox.Home> <5562AC10.8040702@sentry.org> <20150525174007.GA6272@WorkBox.Home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 25 May 2015, Brandon Wandersee wrote: > On 05/25, Trevor Roydhouse wrote: >> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html >> >> Cheers, >> TREV. >> > > Thanks for the link, Trevor. I enabled DDB in the kernel ("options DDB") in > order to prevent the reboot and learned that the VirtualBox kernel module was > causing the hold-up (I use VirtualBox very often, so I load the module at > start-up). I'd forgotten to *rebuild the module after updating the kernel.* I > feel foolish for having forgotten that---I've been using VirtualBox for > years---but all is well now. Thanks for the pointers, and sorry for cluttering > the list with such an inane issue. The quote in my signature seems fitting in > this case. Anyway, take care, all. This bit me also. I usually do not rebuild port kernel modules until after a reboot in the new system, and this is the first time that there was a problem with that. A boot from mfsBSD and temporarily commenting out vboxdrv_load="YES" in /boot/loader.conf was the workaround.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1505260834050.26442>