From owner-freebsd-current@FreeBSD.ORG Wed Aug 10 06:40:12 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1DD916A41F; Wed, 10 Aug 2005 06:40:12 +0000 (GMT) (envelope-from ssouhlal@FreeBSD.org) Received: from efnet-math.org (efnet-math.org [69.60.109.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36D8243D49; Wed, 10 Aug 2005 06:40:12 +0000 (GMT) (envelope-from ssouhlal@FreeBSD.org) Received: from [151.28.103.11] (ppp-11-103.28-151.libero.it [151.28.103.11]) (authenticated bits=0) by efnet-math.org (8.13.1/8.13.1) with ESMTP id j7A6e37t007832 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 10 Aug 2005 02:40:07 -0400 In-Reply-To: <20050809235550.GA8692@freefall.freebsd.org> References: <200508092233.14912.thierry@herbelot.com> <20050809235550.GA8692@freefall.freebsd.org> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Suleiman Souhlal Date: Wed, 10 Aug 2005 08:39:52 +0200 To: Alexander Kabaev X-Mailer: Apple Mail (2.733) Cc: freebsd-current@FreeBSD.org, Thierry Herbelot Subject: Re: panic: lock (sleep mutex) vnode interlock not locked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 06:40:12 -0000 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 >> > > > 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