From owner-freebsd-current  Thu Apr 10 04:25:58 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA29845
          for current-outgoing; Thu, 10 Apr 1997 04:25:58 -0700 (PDT)
Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29822
          for <freebsd-current@freebsd.org>; Thu, 10 Apr 1997 04:25:49 -0700 (PDT)
Received: (from daemon@localhost)
	by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id VAA09315;
	Thu, 10 Apr 1997 21:25:34 +1000
Received: by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a)
	id UAA04428; Thu, 10 Apr 1997 20:47:35 +1000 (EST)
Date: Thu, 10 Apr 1997 20:47:35 +1000 (EST)
From: Stephen McKay <syssgm@dtir.qld.gov.au>
Message-Id: <199704101047.UAA04428@ogre.dtir.qld.gov.au>
To: Steven Wallace <swallace@ece.uci.edu>
cc: freebsd-current@freebsd.org, syssgm@dtir.qld.gov.au
Subject: Re: NFS/mmap freeze in 2.2R
X-Newsreader: NN version 6.5.0 #1 (NOV)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Steven Wallace <swallace@ece.uci.edu> wrote:

>I have discovered how to freeze the system over an NFS mounted filesystem.
>If you map a file over NFS read/write and shared, write
>to the area in memory, and then have another program read that nfs file,
>the system will freeze.  The freeze is kindof wierd though.
>It appears that the kernel is still running somehow. 
>I can change the sysconts vty's but typing and all other processes
>are frozen and not running.

This is awfully similar to my problem (see my NFS stress test post of a
few days ago).  I'm about to follow-up on that thread.  Take a peek.

Stephen.