From owner-freebsd-current  Fri Apr 19 18:35:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA16135
          for current-outgoing; Fri, 19 Apr 1996 18:35:11 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA16130
          for <current@freebsd.org>; Fri, 19 Apr 1996 18:35:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id SAA00247 for <current@freebsd.org>; Fri, 19 Apr 1996 18:09:39 -0700 (PDT)
To: current@freebsd.org
Subject: Anyone else notice NFS broken in -current?
Date: Fri, 19 Apr 1996 18:09:39 -0700
Message-ID: <245.829962579@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Running the latest 2.2 kernels on two boxes here, I can only use NFS
for a short time before any process doing NFS I/O hangs.  After awhile
of this, one of the systems will then reset to the BIOS.

This and other reports now leads me to say that NFS is very, very
broken.  The only question is - who broke it, and when?

					Jordan