From owner-freebsd-emulation@FreeBSD.ORG Wed Sep 23 18:33:47 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 E70471065672; Wed, 23 Sep 2009 18:33:46 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id A71D78FC0C; Wed, 23 Sep 2009 18:33:46 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 108421E0061B; Wed, 23 Sep 2009 20:33:45 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.3/8.14.3) with ESMTP id n8NIWNNS002448; Wed, 23 Sep 2009 20:32:23 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.3/8.14.3/Submit) id n8NIWNVw002447; Wed, 23 Sep 2009 20:32:23 +0200 (CEST) (envelope-from nox) Date: Wed, 23 Sep 2009 20:32:23 +0200 (CEST) From: Juergen Lock Message-Id: <200909231832.n8NIWNVw002447@triton8.kn-bremen.de> To: scf@FreeBSD.org X-Newsgroups: local.list.freebsd.emulation In-Reply-To: Organization: home 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: Wed, 23 Sep 2009 18:33:47 -0000 In article you write: >While I have had no trouble with two systems running with the tap patch, >I am experiencing some lockups when using the vboxnet* drivers. > >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. >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. >3. The last log is a LOR, but it may not be related to VirtualBox. >[...] It seems the attachments got stripped... Juergen