From owner-freebsd-current  Sat Jun  7 07:27:23 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA19422
          for current-outgoing; Sat, 7 Jun 1997 07:27:23 -0700 (PDT)
Received: from bmccane.uit.net (bmccane.uit.net [208.129.189.48])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19407
          for <current@freebsd.org>; Sat, 7 Jun 1997 07:26:59 -0700 (PDT)
Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1])
	by bmccane.uit.net (8.8.5/8.8.5) with ESMTP id JAA19490
	for <current@freebsd.org>; Sat, 7 Jun 1997 09:26:38 -0500 (CDT)
Message-Id: <199706071426.JAA19490@bmccane.uit.net>
X-Mailer: exmh version 2.0gamma 1/27/96
To: current@freebsd.org
Subject: Lockup
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 07 Jun 1997 09:26:38 -0500
From: Wm Brian McCane <root@bmccane.uit.net>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I have found an `interesting' lockup in -current involving NFS.  If I have a 
filesystem mounted from my server machine onto one of my client machines, and 
then unmount the filesystem on the server, the next time I type `df' the 
client stops working.  No panic, nothing just dead.  In X the mouse stops 
moving, and I cannot switch to a text console.  On a text console, I cannot 
get any response to the keyboard, including Ctrl-Alt-Del.  I was thinking 
about adding DDB to the kernel, but with this type of lockup, I suspect it 
won't do any good.  I discovered this the other night when I developed a 
couple of bad blocks on a drive and repartitioned it to allow bad144 bad 
sector forwarding, before reloading from tape.

	brian