From owner-freebsd-current  Fri Jan 31 12:47:11 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA11481
          for current-outgoing; Fri, 31 Jan 1997 12:47:11 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA11476
          for <current@freebsd.org>; Fri, 31 Jan 1997 12:47:08 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id HAA30656; Sat, 1 Feb 1997 07:44:31 +1100
Date: Sat, 1 Feb 1997 07:44:31 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701312044.HAA30656@godzilla.zeta.org.au>
To: bde@zeta.org.au, skynyrd@opus.cts.cwu.edu
Subject: Re: nfs hang
Cc: current@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I had a similar hang with a -current from a few days ago.  I v2 mounted
>the -current box's /usr from a releng_2_2 box and was in the middle of a
>cvs update on the -current machines /usr/src when everything stopped.  I
>was still able to telnet to the current machine and access that file
>system ok, but the cvs process on the 2_2 machine was hung in an nfs state
>(that I don't remember at the moment :(

I've only seen problems with localhost.  They were more serious (accesses
to local disks hung and panic in ddb recursed.  I used ps in ddb to look
at the state).

>Can you suggest a debugging strategy to help me pin this down further?

ps in ddb can be useful, but here it would probably just confirm that
nfs is hung.

Bruce