From owner-freebsd-current@FreeBSD.ORG  Fri Jun 11 15:21:49 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 BDEF716A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 11 Jun 2004 15:21:49 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 62AFF43D31
	for <freebsd-current@freebsd.org>;
	Fri, 11 Jun 2004 15:21:49 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i5BFKaN2067012;
	Fri, 11 Jun 2004 11:20:36 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i5BFKaMp067009;
	Fri, 11 Jun 2004 11:20:36 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Fri, 11 Jun 2004 11:20:36 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: othermark <atkin901@yahoo.com>
In-Reply-To: <cacg79$hmh$1@sea.gmane.org>
Message-ID: <Pine.NEB.3.96L.1040611105034.66561A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: Today's -current panics
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: Fri, 11 Jun 2004 15:21:49 -0000

On Fri, 11 Jun 2004, othermark wrote:

> Robert Watson wrote:
> > It would be extremely helpful if you could figure out where in the kernel
> > 0xc04cbf38 is.  You should be able to do this using a kernel on disk;
> > debugging, etc, is not necessary.  If possible, DDB stack traces or the
> > results of gdb on a dump would also be extremely helpful.
> 
> I get a very similar stack track traversing through sossend(), under
> heavy NFS load on a 1GB machine.  Note the panic message here, and the
> peculiarity that previous incarnations of -current did not panic under
> similar load.  It is highly reproduceable via a 'make installworld' via
> NFS with /usr/src and /usr/obj mounted.  The NFS serving machine will
> always panic using vanilla GENERIC:

Hrmm.  It's certainly similar, but it's not clear to me that it's
necessarily related (although I wouldn't preclude that).  Could you tell
me what date you cvsup'd this tree?

Also, since you have a dump (yay!), could you try running vmstat -m,
vmstat -z, and netstat -mb against the dump?  It could be that a bug was
introduced in nfsd that leaks mbufs or the like, or it could be a nit in
mbuma.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Senior Research Scientist, McAfee Research