From owner-freebsd-current@FreeBSD.ORG  Wed Dec  3 11:43:13 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 8FD5F16A4CE; Wed,  3 Dec 2003 11:43:13 -0800 (PST)
Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A402543FE9; Wed,  3 Dec 2003 11:43:12 -0800 (PST)
	(envelope-from mckusick@beastie.mckusick.com)
Received: from beastie.mckusick.com (localhost [127.0.0.1])
	by beastie.mckusick.com (8.12.8/8.12.3) with ESMTP id hB3JhBaG060203;
	Wed, 3 Dec 2003 11:43:11 -0800 (PST)
	(envelope-from mckusick@beastie.mckusick.com)
Message-Id: <200312031943.hB3JhBaG060203@beastie.mckusick.com>
To: Robert Watson <rwatson@FreeBSD.org>
In-Reply-To: Your message of "Wed, 03 Dec 2003 08:19:54 EST."
             <Pine.NEB.3.96L.1031203081806.82018B-100000@fledge.watson.org> 
Date: Wed, 03 Dec 2003 11:43:11 -0800
From: Kirk McKusick <mckusick@beastie.mckusick.com>
cc: Jun Kuriyama <kuriyama@imgsrc.co.jp>
cc: current@FreeBSD.org
Subject: Re: -current lockup (how to diagnose?)
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: Wed, 03 Dec 2003 19:43:13 -0000

I am guessing that some of the recent locking changes are causing
the problem.  Unfortunately I am on the road now through Jan 4th,
so will not be in a position to look at it. Hopefully one of the
folks working on getting the SMP pushed down through the filesystem
(Jeff Roberson, John Baldwin, or Alan Cox) will have some idea what
broke recently. I would try looking at which process holds the
buffer lock that the find is trying to get. You can usually unravel
the chain of locks to eventually find what pair of events lead to
the deadlock. It definitely helps to have DEBUG_LOCKS compiled into
your kernel.

	Kirk McKusick