From owner-freebsd-hackers Fri Jun 11 19:39:15 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 3703314CD4 for ; Fri, 11 Jun 1999 19:38:59 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA81167; Fri, 11 Jun 1999 22:38:53 -0400 (EDT) Message-Id: <199906120238.WAA81167@cs.rpi.edu> To: Conrad Minshall Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: -STABLE, panic #15 In-Reply-To: Message from Conrad Minshall of "Fri, 11 Jun 1999 16:41:29 PDT." Date: Fri, 11 Jun 1999 22:37:15 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I have determined (just today) that the PANIC is only Solaris, and only with NFSv3 (It may be posssible with NFSv2, but my program doesn't do it as quickly.). I have a NFS traffic dump of a mere 19K of all nfs traffic to the machine before the panic. Also, it does NOT ALWAYS cause a panic. 95% of the time it does, the rest of the time it just stops serving NFS. I had it happen again now, and I looked and noticed that all NFSds were in disk-wait, in channel "inode". Things are starting to smell a bit sweater for me. I continue to look arround the kernel source for clues, but it is difficult. a copy of the packet dump is at: http://www.cs.rpi.edu/~crossd/FreeBSD/patoot.1 Please help. -- 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