From owner-freebsd-current@FreeBSD.ORG  Tue Nov 11 17:37:07 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 17BC916A4CE
	for <current@freebsd.org>; Tue, 11 Nov 2003 17:37:07 -0800 (PST)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CB70943FCB
	for <current@freebsd.org>; Tue, 11 Nov 2003 17:37:05 -0800 (PST)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id BC07F72DA8; Tue, 11 Nov 2003 17:37:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id BA4B272DA2
	for <current@freebsd.org>; Tue, 11 Nov 2003 17:37:05 -0800 (PST)
Date: Tue, 11 Nov 2003 17:37:05 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: current@freebsd.org
In-Reply-To: <200311111620.13378.x@Vex.Net>
Message-ID: <20031111173123.L66327@carver.gumbysoft.com>
References: <200311101744.hAAHiefC008462@spider.deepcore.dk>
 <200311111620.13378.x@Vex.Net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Still getting NFS client locking up
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, 12 Nov 2003 01:37:07 -0000

On Tue, 11 Nov 2003, Tim Middleton wrote:

> The server is a P3-1ghz Intel STL2 box, with 1 gig of ram. Using the onboard
> fxp ethernet at 100baseTX. It is not using dhcp. Nothing much else is running
> on this server box as I'm just testing it. When the server locks the box can
> not even be pinged.

Can you set up a serial console on this system?  If so, enable these
kernel options:
options DDB
options WITNESS
options INVARIANTS
options INVARIANTS_SUPPORT
options BREAK_TO_DEBUGGER

Boot through the serial console then trigger the bug and send a break from
serial.  If you drop into ddb, then its a Giant deadlock.

If you can get that, then do 'show locks' from ddb to get a list of
potential culprits, and 'tr' for what its stuck doing.

The kernel handbook section on kernel debugging will be a useful read.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org