Date: Wed, 23 Sep 2009 20:32:23 +0200 (CEST) From: Juergen Lock <nox@jelal.kn-bremen.de> To: scf@FreeBSD.org Cc: freebsd-emulation@FreeBSD.org Subject: Re: Panic with vboxnet drivers Message-ID: <200909231832.n8NIWNVw002447@triton8.kn-bremen.de> In-Reply-To: <alpine.BSF.2.00.0909221337580.13791@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <alpine.BSF.2.00.0909221337580.13791@thor.farley.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909231832.n8NIWNVw002447>