From owner-freebsd-current@FreeBSD.ORG Sat Oct 31 22:03:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 009E2106566B for ; Sat, 31 Oct 2009 22:03:01 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CF8678FC08 for ; Sat, 31 Oct 2009 22:03:00 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 56AF246B03; Sat, 31 Oct 2009 18:03:00 -0400 (EDT) Date: Sat, 31 Oct 2009 22:03:00 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Matthias Rampke In-Reply-To: <31d643300910311306m6caa73cfi8930465e43773ff4@mail.gmail.com> Message-ID: References: <31d643300910311245r593326e1me8574bdff5198b51@mail.gmail.com> <31d643300910311306m6caa73cfi8930465e43773ff4@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Host OS (OS X 10.6.1) panic when booting 8.0-RC2 in VirtualBox 3.0.10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Oct 2009 22:03:01 -0000 On Sat, 31 Oct 2009, Matthias Rampke wrote: > On Sat, Oct 31, 2009 at 8:45 PM, Matthias Rampke > wrote: > >> I have been experiencing reproducible kernel panics in Mac OS X 10.6.1 when >> booting 8.0-RC1 and -RC2 (amd64) in a VirtualBox VM. >> >> I had a (mostly pristine) 7.2-RELEASE running in this VM and tried to >> upgrade to 8.0-RC2 with freebsd-update. It could well be that a bug in FreeBSD is triggering the bug in VirtualBox, but we're unlikely to make much headway debugging the FreeBSD bug (if any) until the bug in VirtualBox is diagnosed/fixed. I'm not sure what the normal debugging procedure for vbox panics on Mac OS X is, but I'd suggest making a backup copy of the bad VM so that you can trigger it on demand later. > This does not happen in a new, freshly installed VM. Now it hangs at usbus > initialization, but I suppose that's a different story (the pains of using > USB with VirtualBox, they never end). This, on the other hand, could be our bug; there's a new USB stack in 8.0. I suggest creating a new thread for that issue with a usb-related subject line to make sure the right folk see it. Robert