From owner-freebsd-stable  Mon Aug  5 15:02:21 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA25207
          for stable-outgoing; Mon, 5 Aug 1996 15:02:21 -0700 (PDT)
Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA25198
          for <freebsd-stable@freebsd.org>; Mon, 5 Aug 1996 15:02:17 -0700 (PDT)
Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id RAA27788; Mon, 5 Aug 1996 17:02:07 -0500 (CDT)
Message-Id: <199608052202.RAA27788@sierra.zyzzyva.com>
To: Tom Samplonius <tom@uniserve.com>
cc: Randy Terbush <randy@zyzzyva.com>, freebsd-stable@freebsd.org
Subject: Re: ep0 problems and the stable tree 
In-reply-to: tom's message of Mon, 05 Aug 1996 10:52:18 -0700.
         <Pine.BSF.3.91.960805104646.3871A-100000@haven.uniserve.com> 
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 05 Aug 1996 17:02:06 -0500
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


3c509 combo

Would it not evenutally catch up?


> 
> On Mon, 5 Aug 1996, Randy Terbush wrote:
> 
> > I'm would like to add the following to my previous post and
> > bring this on to the current list, since the -stable list appears
> > to be deserted...
> > 
> > I can further pin this behavior down to TCP NFS connections.
> > UDP does not seem to be aflicted, but it is easily recreated
> > over a TCP NFS connection.
> > 
> > Is there any chance that the "grinding to a halt" reports on
> > -current are network related?
> > 
> > > I've seen a lot of discussion about the ep driver getting broken late
> > > in the 2.1.5 release. Should I still be seeing this from sources dated
> > > 
> > > sierra:/sys/i386/isa
> > > #> ll if_ep*
> > > -rw-r--r--  1 root  wheel  36464 Jul 15 23:10 if_ep.c
> > > -rw-r--r--  1 root  wheel  36457 May 26 14:54 if_ep.c.orig
> > > -rw-r--r--  1 root  wheel  13946 Mar 31 23:08 if_epreg.h
> > > 
> > > Aug  3 16:11:25 sierra /kernel: ep0: Status: 2002 (input buffer overflow)
> > > Aug  3 16:13:49 sierra /kernel: ep0: Status: 2002 (input buffer overflow)
> > > Aug  3 16:13:52 sierra /kernel: ep0: Status: 2002 (input buffer overflow)
> > > 
> > > 
> > > The net result is that a new NFS client on the net is suddenly freezing
> > > quite frequently. Killing and restarting the 'nfsd' processes on the
> > > server fix the problem.
> 
>   What kind of 3COM card are you using?  Some 3COM cards have very 
> limited buffer space (8k ?), and will get buffer overflow very easily if 
> your computer can't keep service interupts fast enough.
> 
>   This would explain why TCP would be effect, becasue TCP would transfer 
> a whole window of packets at once, which would flood your buffer space.
> 
>   BTW, I ignored your first message to -stable because your never said 
> what kind of card you were using, because if you are using one of the 
> good cards, I'd wasting your and my time.
> 
> Tom