From owner-freebsd-bugs  Wed May 28 14:50:45 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA05282
          for bugs-outgoing; Wed, 28 May 1997 14:50:45 -0700 (PDT)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA05275
          for <freebsd-bugs@freefall.FreeBSD.org>; Wed, 28 May 1997 14:50:40 -0700 (PDT)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA10942; Wed, 28 May 1997 17:50:05 -0400
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 28 May 1997 17:50 EDT
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id OAA24457; Wed, 28 May 1997 14:09:56 -0400 (EDT)
Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id OAA06044; Wed, 28 May 1997 14:17:20 -0400 (EDT)
Date: Wed, 28 May 1997 14:17:20 -0400 (EDT)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199705281817.OAA06044@lakes.water.net>
To: rodigue@ibm.net, ponds!freefall.cdrom.com!freebsd-bugs
Subject: Re: kern/3674: NFS in 2.2 RELEASE hangs.
Content-Type: text
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.
> 

 If I'm not mistaken - 'cp' using mmap to actually copy the file.
You could have an mmap or other VM problem here.  I recall similar
problems in the 1.1.5 time frame.  At that time, it was decided to
not use mmap in 'cp'...

	- Dave Rivers -