From owner-freebsd-bugs  Tue May 27 19:10:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA16227
          for bugs-outgoing; Tue, 27 May 1997 19:10:03 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA16221;
          Tue, 27 May 1997 19:10:01 -0700 (PDT)
Date: Tue, 27 May 1997 19:10:01 -0700 (PDT)
Message-Id: <199705280210.TAA16221@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Jose A Rodriguez <rodigue@ibm.net>
Subject: Re: kern/3674: NFS in 2.2 RELEASE hangs.
Reply-To: Jose A Rodriguez <rodigue@ibm.net>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3674; it has been noted by GNATS.

From: Jose A Rodriguez <rodigue@ibm.net>
To: freebsd-gnats-submit@freebsd.org, dfr@nlsystems.com
Cc:  Subject: Re: kern/3674: NFS in 2.2 RELEASE hangs.
Date: Tue, 27 May 1997 22:04:16 -0400

 When I read that the problem might be caused by a fast server
 overwhelming a slower client, I did the following to prevent IP
 fragmentation:
 
 mount -t nfs -o -r=1024 remote_machine:/remote_directory  /mnt
 
 Then  I did
 
 	cp /mnt/remote_file local_file
 
 and after a few seconds I started to get kernel panics ! (Page faults
 while in kernel mode, LRU queue inconsistent, and other nasty messages).
 
 By the way, the client's network card is AMD PCNET (pci & isa), 
 at least this is what Win95 reports.