From owner-freebsd-bugs@FreeBSD.ORG  Sun May 29 23:00:03 2011
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 55BD4106566B;
	Sun, 29 May 2011 23:00:03 +0000 (UTC)
	(envelope-from gavin@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 20CF48FC0C;
	Sun, 29 May 2011 23:00:03 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4TN03sT045865;
	Sun, 29 May 2011 23:00:03 GMT
	(envelope-from gavin@freefall.freebsd.org)
Received: (from gavin@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4TN02S9045861;
	Sun, 29 May 2011 23:00:02 GMT (envelope-from gavin)
Date: Sun, 29 May 2011 23:00:02 GMT
Message-Id: <201105292300.p4TN02S9045861@freefall.freebsd.org>
To: gavin@FreeBSD.org, kmacy@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: gavin@FreeBSD.org
Cc: 
Subject: Re: kern/116133: Recursive lock panic when w_mtx falls into DELAY
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2011 23:00:03 -0000

Synopsis: Recursive lock panic when w_mtx falls into DELAY

Responsible-Changed-From-To: kmacy->freebsd-bugs
Responsible-Changed-By: gavin
Responsible-Changed-When: Sun May 29 22:47:50 UTC 2011
Responsible-Changed-Why: 
kmacy has asked for all of his PRs to be reassigned back to the pool.

It is not clear to me whether this is still an issue or not with the
current code.  Due to refactoring, the lock init code is now in
sys/x86/isa/clock.c.  The lock is now marked as MTX_NOPROFILE, it's
not clear to me if this has the same effect on the panic as
MTX_NOWITNESS.

http://www.freebsd.org/cgi/query-pr.cgi?pr=116133