From owner-freebsd-current@FreeBSD.ORG  Wed Jul  9 20:22:04 2003
Return-Path: <owner-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 2D9C737B401
	for <freebsd-current@FreeBSD.org>;
	Wed,  9 Jul 2003 20:22:04 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6B0DF43FBF
	for <freebsd-current@FreeBSD.org>;
	Wed,  9 Jul 2003 20:22:03 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h6A3LtM7014326;
	Wed, 9 Jul 2003 20:21:59 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200307100321.h6A3LtM7014326@gw.catspoiler.org>
Date: Wed, 9 Jul 2003 20:21:55 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: peter@holm.cc
In-Reply-To: <20030709091929.GA25681@peter.osted.lan>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
Subject: Re: Deadlock
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jul 2003 03:22:04 -0000

On  9 Jul, Peter Holm wrote:
> Here's a trace from a deadlock in a kernel from Jul 8 13:51 UTC:
> 
> http://people.freebsd.org/~pho/stress/cons36.html

It sure looks like a mutex implementation problem.  Process 4616 is
waiting on pool mutex c05dd04c, but this process doesn't show up on the
blocked queue for the mutex.  That sounds a lot like the bug fixed in
rev 1.129 of kern_mutex.c.