From owner-freebsd-current@FreeBSD.ORG  Thu Feb  5 11:06:13 2004
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 A105116A4CF; Thu,  5 Feb 2004 11:06:13 -0800 (PST)
Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU
	[128.205.32.2])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0652943D48; Thu,  5 Feb 2004 11:06:10 -0800 (PST)
	(envelope-from kensmith@cse.Buffalo.EDU)
Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1])
	i15J4bTr021802;	Thu, 5 Feb 2004 14:04:37 -0500 (EST)
Received: (from kensmith@localhost)
	by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i15J4bOf021801;
	Thu, 5 Feb 2004 14:04:37 -0500 (EST)
Date: Thu, 5 Feb 2004 14:04:37 -0500
From: Ken Smith <kensmith@cse.Buffalo.EDU>
To: "Brian F. Feldman" <green@freebsd.org>
Message-ID: <20040205190436.GA21606@electra.cse.Buffalo.EDU>
References: <Peter_Losher@isc.org> <200402041823.36188.Peter_Losher@isc.org>
	<200402051852.i15Iq81n067069@green.bikeshed.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200402051852.i15Iq81n067069@green.bikeshed.org>
User-Agent: Mutt/1.4.1i
cc: Peter Losher <Peter_Losher@isc.org>
cc: current@freebsd.org
Subject: Re: Odd quirks after updating to 5.2...
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, 05 Feb 2004 19:06:13 -0000

On Thu, Feb 05, 2004 at 01:52:08PM -0500, Brian F. Feldman wrote:

> FWIW, I've seen a deadlock similar to this.  I can get it when unmounting a 
> UFS filesystem after writing to it (but haven't seen it before unmount).

I have a machine sitting at the ddb prompt in exactly this state.
Anyone know how to dig something useful out of the current state
the buffer cache is in?  I know how to find out what vnodes are
locked but don't know how to go from that to see what underlying
buffers are causing the problem.

I should be able to cause a dump of the machine as well but it has
2Gb of memory in it so transferring the dump to someone other than
me who could look at it might be painful...

-- 
						Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |