From root@sabre.velocet.net Sat Mar 13 15:55:17 1999
Return-Path: <root@sabre.velocet.net>
Received: from sabre.velocet.net (monmouth.velocet.net [198.96.118.66])
	by hub.freebsd.org (Postfix) with ESMTP id 5360314F1B
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 13 Mar 1999 15:55:03 -0800 (PST)
	(envelope-from root@sabre.velocet.net)
Received: (from root@localhost)
	by sabre.velocet.net (8.9.2/8.9.2) id XAA22999;
	Sat, 13 Mar 1999 23:54:44 GMT
	(envelope-from root)
Message-Id: <199903132354.XAA22999@sabre.velocet.net>
Date: Sat, 13 Mar 1999 23:54:44 GMT
From: dgilbert@velocet.net
Sender: root@sabre.velocet.net
Reply-To: dgilbert@velocet.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: tx0 slows to crawl
X-Send-Pr-Version: 3.2

>Number:         10575
>Category:       kern
>Synopsis:       tx0 devices slow to crawl over time
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar 13 16:00:01 PST 1999
>Closed-Date:    Sun Mar 14 08:43:01 PST 1999
>Last-Modified:  Sun Mar 14 08:50:00 PST 1999
>Originator:     David Gilbert
>Release:        FreeBSD 3.1-RELEASE i386
>Organization:
Velocet Communications
>Environment:

	I have a number of machines with one or more Etherpower II
ethernet cards in them.  The number of cards does not appear to
matter.  This bug appears in both FreeBSD-3.0 and FreeBSD-3.1

>Description:

	Left to it's own, the tx0 driver will start to 'hold' packets
until the system is virtually unusuable.  A typical symptom is where
pinging the machine will yield an X second pause followed by a spurt 
of X ping packets.

	The strange thing about this problem is that trafic causes
this problem to be less frequent.  More traffic on an interface will
make the problem happen far less often and far less severely.

	On a machine that has many websites and an average 40K/s
traffic and on a machine that has two of these cards to be a router
and firewall, the problem takes as much as a week to manifest
and X will be 1 or 2.  On a machine with very little traffic (not
entirely in production yet) the problem will normally develop
over about 24 hours and X will be 16.

>How-To-Repeat:

	Use a tx0 card in a machine, and let it sit almost-idle
for 24 hours.

>Fix:
	
	I have found that ifconfig up is not enough to fix the problem
(as I have heard about the ep0 driver).  I have found that ifconfig down
followed by ifconfig up is required.




>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Sun Mar 14 08:43:01 PST 1999 
State-Changed-Why:  
Duplicate of kern/10575. 

From: Sheldon Hearn <sheldonh@iafrica.com>
To: David Gilbert <dgilbert@velocet.net>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/10575
Date: Sun, 14 Mar 1999 18:47:11 +0200

 Synopsis: tx0 devices slow to crawl over time
 
 It's actually a duplicate of kern/10535.
 
 Sorry,
 Sheldon.
 
>Unformatted:
