Date: Wed, 30 Sep 2009 07:36:55 +0200 From: Fredrik Lindberg <fli@shapeshifter.se> To: "Sean C. Farley" <scf@FreeBSD.org> Cc: freebsd-emulation@FreeBSD.org Subject: Re: Panic with vboxnet drivers Message-ID: <4AC2EE77.4090509@shapeshifter.se> In-Reply-To: <alpine.BSF.2.00.0909282037290.1735@thor.farley.org> References: <alpine.BSF.2.00.0909221337580.13791@thor.farley.org> <4AC120F6.7090701@shapeshifter.se> <alpine.BSF.2.00.0909282037290.1735@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean C. Farley wrote: >>> 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. > Great, I'll submit it upstreams as soon as possible. Fredrik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AC2EE77.4090509>