From owner-freebsd-hackers Fri Jun 11 20:28:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id C98CA14BF3 for ; Fri, 11 Jun 1999 20:28:22 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA81593; Fri, 11 Jun 1999 23:28:19 -0400 (EDT) Message-Id: <199906120328.XAA81593@cs.rpi.edu> To: "David E. Cross" Cc: Conrad Minshall , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: -STABLE, panic #15 In-Reply-To: Message from "David E. Cross" of "Fri, 11 Jun 1999 23:00:05 EDT." <199906120301.XAA81383@cs.rpi.edu> Date: Fri, 11 Jun 1999 23:28:18 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I am hot on the trail... I have found a comonality(sp?) between at least 2 of the Panics. (the 2 I listed)... it is as follows: request: create cp1 request: create cp1 reply: ok reply: error, file exists request: lookup request: lookup (never any response to those.) I am guessting that: the second create gets a lock but never releases it under these conditions. the lookup comes along and *wham*. Note, that almost all of these panics occur within the nfs_lookup routines. I have *one* panic out of all of these (with lockmgr....) that doesn't after I nail this down, I will try to trace that down if it is a seperate panic. I am very close on this, I would feel bad and great at the same time if someone beats me to this. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message