Date: Wed, 10 Aug 2005 08:39:52 +0200 From: Suleiman Souhlal <ssouhlal@FreeBSD.org> To: Alexander Kabaev <kan@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, Thierry Herbelot <thierry@herbelot.com> Subject: Re: panic: lock (sleep mutex) vnode interlock not locked Message-ID: <A1B9525E-23CB-4ABF-B31F-EF5FDC7BC23B@FreeBSD.org> In-Reply-To: <20050809235550.GA8692@freefall.freebsd.org> References: <200508092233.14912.thierry@herbelot.com> <20050809235550.GA8692@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On Aug 10, 2005, at 1:55 AM, Alexander Kabaev wrote: > On Tue, Aug 09, 2005 at 10:33:12PM +0200, Thierry Herbelot wrote: > >> Hello, >> >> I'm seeing the above panic on two machines (SMP BP6 and a >> notebook) with >> recent -Current (certainly "heisenbug" : the same kernel runs >> happily on the >> notebook). >> The panic log on the SMP machine follows. >> >> TfH >> > <SKIP> > > Hi, > > could you try an patch below? If you look at the place where the panic is happening, vlrureclaim(), you'll notice that it shouldn't be possible for vgonel() to be called on a doomed vnode. It seems, from KTR traces gotten by kris, that there is a race between vlrureclaim() and vnlru_free() (called also in getnewvnode()), but I've been unable to find it. -- Suleiman Souhlal | ssouhlal@vt.edu The FreeBSD Project | ssouhlal@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A1B9525E-23CB-4ABF-B31F-EF5FDC7BC23B>