From owner-freebsd-hackers Fri Feb 11 16:16:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id 0D1B13DB6 for ; Fri, 11 Feb 2000 16:16:09 -0800 (PST) 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 TAA82907 for ; Fri, 11 Feb 2000 19:16:00 -0500 (EST) Message-Id: <200002120016.TAA82907@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: hard lock under 3.4-STABLE Date: Fri, 11 Feb 2000 19:16:00 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am seeing a situation where a 3.4 system hard-locks while running 3.4 (hard lock being that it does not respond to its serial console, nor is it pingable). I believe (perhaps) that it may be NFS related, with a program running on an NFS client when the executable itself is deleted from the server (although I haven't seen that style of panic in quite some time, and it is usually has a couple of lines earlier in the output to the effect that it lost its backing store. I realize that information is sparse in this, but that is because the information that I have is equally sparse... I have no kernel messages, I cannot drop into the kernel debugger, and no crashdump is ever created (I need to hit the reset button to recover.) I am trying to reproduce a test case, but it is difficult not knowing what has caused the problems in the first place. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD 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