From owner-freebsd-questions  Tue Jul 29 10:20:23 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA00512
          for questions-outgoing; Tue, 29 Jul 1997 10:20:23 -0700 (PDT)
Received: from gdi.uoregon.edu (cisco-ts7-line13.uoregon.edu [128.223.150.60])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA00506
          for <freebsd-questions@FreeBSD.ORG>; Tue, 29 Jul 1997 10:20:16 -0700 (PDT)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id KAA08631;
          Tue, 29 Jul 1997 10:20:04 -0700 (PDT)
Date: Tue, 29 Jul 1997 10:20:03 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Dave Babler <dbabler@Rigel.orionsys.com>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Network/Routed Problem
In-Reply-To: <Pine.BSI.3.95.970728100916.6750C-100000@Rigel.orionsys.com>
Message-ID: <Pine.BSF.3.96.970729101727.8468R-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 28 Jul 1997, Dave Babler wrote:

> > Unfortunately the support for the Intel EtherExpress series leaves much to
> > be desired.  We had to abandon an EtherExpress16 on our 486 server due to
> > occaisional problems and traded it in for a totally flawless NE2000.  
> > 
> 
> What problems did it have, Doug? I'm running this on a 486DX2-66
> currently.

It'd interrupt-lock and thus completely disable network traffic.  Fixing
it required a cold boot.  We could do this pretty easily by heavily
loading the machine (ping -f from a P120 with a PCI ethernet card would do
it). Basically, it couldn't handle the load.

> Well, I suppose if I have to, I will... except that it worked flawlessly
> up until the driver was merged with the ix cards. On the plus side, I can
> now run trafshow and other network tools - on the down side, that
> apparently causes it to lock up in an unexplained way. Just *how* it can
> survive EEPROM reprogramming and powerdowns and then suddenly start
> working again is pure voodoo.

Absolutely.  Gotta keep up on your sacrifices, have to keep those voodoo
gods happy....which reminds me, it's about time for my boxes.  Call in the
baby goat and the brazier...:) 

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major
Spam routed to /dev/null by Procmail    | Death to Cyberpromo