From owner-freebsd-hackers  Tue May 18  1:39: 4 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
	by hub.freebsd.org (Postfix) with SMTP id 51C5414FDD
	for <hackers@freebsd.org>; Tue, 18 May 1999 01:38:59 -0700 (PDT)
	(envelope-from will@ns.oeno.com)
Received: (qmail 23096 invoked by uid 1001); 18 May 1999 08:38:54 -0000
To: crossd@cs.rpi.edu (David E. Cross)
Cc: hackers@freebsd.org
Subject: Re: Repeatable kernel panic for 3.2-RELEASE NFS server
References: <199905180532.BAA72781@cs.rpi.edu>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 18 May 1999 11:37:03 +0300
In-Reply-To: crossd@cs.rpi.edu's message of "18 May 1999 08:32:51 +0300"
Message-ID: <86g14u6afk.fsf@not.demophon.com>
Lines: 11
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

crossd@cs.rpi.edu (David E. Cross) writes:

> One of our users way able to reliably crash an NFS server 3 times today.
> I have since copied his program and have reliably crashed a seperate and
> unloaded machine with the exact same panic, "lockmgr: locking against
> myself".  I check the recent DG patches that went in after -RELEASE and they

Are you sure this is NFS related?

I can certainly reliably reproduce that and other panics (reported in
kern/11629, includes a fix).


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message