From owner-freebsd-stable@FreeBSD.ORG  Tue May 26 14:37:11 2015
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F005B2A3
 for <freebsd-stable@freebsd.org>; Tue, 26 May 2015 14:37:11 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id A2E489EB
 for <freebsd-stable@freebsd.org>; Tue, 26 May 2015 14:37:11 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.9/8.14.9) with ESMTP id t4QEb2Ij029724
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 26 May 2015 08:37:02 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id t4QEb2m3029721;
 Tue, 26 May 2015 08:37:02 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
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
In-Reply-To: <20150525174007.GA6272@WorkBox.Home>
Message-ID: <alpine.BSF.2.20.1505260834050.26442@wonkity.com>
References: <20150525025607.GA1071@WorkBox.Home> <5562AC10.8040702@sentry.org>
 <20150525174007.GA6272@WorkBox.Home>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Tue, 26 May 2015 08:37:02 -0600 (MDT)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 May 2015 14:37:12 -0000

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.