From owner-freebsd-current Sun Dec 29 10:48:30 2002 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 F27E437B401 for ; Sun, 29 Dec 2002 10:48:29 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id CCD3E43EDC for ; Sun, 29 Dec 2002 10:48:28 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 29 Dec 2002 18:46:25 +0000 (GMT) To: ryan beasley Cc: freebsd-current@freebsd.org Subject: Re: panic: lockmgr: draining against myself In-Reply-To: Your message of "Sat, 28 Dec 2002 23:59:19 CST." <20021229055919.GA62145@goddamnbastard.org> Date: Sun, 29 Dec 2002 18:46:25 +0000 From: Ian Dowse Message-ID: <200212291846.aa10883@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021229055919.GA62145@goddamnbastard.org>, ryan beasley writes: > >panic: lockmgr: draining against myself I've just checked in revision 1.426 of vfs_subr.c which may solve this, but I was not able to reproduce it myself. Could you or anybody else who has seen this panic try the above revision to see if it helps? Note that you will need HEAD rather than RELENG_5_0 to get this change. There is probably a better approach to solve the VOP_INACTIVE recursion problem than the one I used though - I think maybe having a vnode flag that remembers whether a VOP_INACTIVE call is necessary would be more general than the VI_DOINGINACT flag. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message