From owner-freebsd-emulation@FreeBSD.ORG Tue Sep 29 01:39:57 2009 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 588461065676 for ; Tue, 29 Sep 2009 01:39:57 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f0f:20:2::11]) by mx1.freebsd.org (Postfix) with ESMTP id 154B98FC14 for ; Tue, 29 Sep 2009 01:39:57 +0000 (UTC) Received: from thor.farley.org (HPooka@thor.farley.org [IPv6:2001:470:1f0f:20:1::5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id n8T1dtLx000605; Mon, 28 Sep 2009 20:39:56 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Mon, 28 Sep 2009 20:39:55 -0500 (CDT) From: "Sean C. Farley" To: Fredrik Lindberg In-Reply-To: <4AC120F6.7090701@shapeshifter.se> Message-ID: References: <4AC120F6.7090701@shapeshifter.se> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-2.8 required=4.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail.farley.org Cc: freebsd-emulation@FreeBSD.org Subject: Re: Panic with vboxnet drivers X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2009 01:39:57 -0000 On Mon, 28 Sep 2009, Fredrik Lindberg wrote: > Sean C. Farley wrote: >> I have five witness logs (attached): >> 1. The first one appeared when I tried to run VirtualBox with >> vboxnetadp loaded via loader.conf. VirtualBox will not be able to >> find the VirtualBox network drivers this way, so I unloaded and >> loaded vboxnetadp from the command line for the following logs. > > Need to look a bit more on this one. Thank you. >> 2. The next three logs are LOR's (sleepable after non-sleepable) >> concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an >> sx. I am not sure I am reading the backtrace correctly. It looks >> like the call to RTSemFastMutexRequest(), which calls sx_xlock(), >> is the effect. I just do not know where the cause, i.e., >> RTSemFastMutexRequest(), is being called. > > Yeah, this was a real one. The call to RTSemFastMutexRequest is inside > the virtual ethernet switch. I've attached a patch that defers > processing to avoid the sleepable after non-sleepable case. Hopefully > this fixes the panic you're seeing as well. Thank you! :) This does fix the panic. Sean -- scf@FreeBSD.org