From owner-freebsd-questions Tue Jul 30 19:19:28 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA25371 for questions-outgoing; Tue, 30 Jul 1996 19:19:28 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA25365 for ; Tue, 30 Jul 1996 19:19:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id TAA00329; Tue, 30 Jul 1996 19:18:59 -0700 (PDT) Message-Id: <199607310218.TAA00329@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Dave Andersen cc: jason@pdh.com (Jason Rhoads), questions@FreeBSD.ORG Subject: Re: Wierd problem with dual ethernet boards In-reply-to: Your message of "Tue, 30 Jul 1996 15:09:06 MDT." <199607302109.PAA12460@shell.aros.net> From: David Greenman Reply-To: dg@root.com Date: Tue, 30 Jul 1996 19:18:59 -0700 Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >AFAIK, it's a bug in some revisions of the EtherExpress card. The fix is >to down and up the interface using ifconfig -- that'll bring it back to >life. Ugly, but it works. > >When we were using one of those cards, I wrote a quick perl script that >ran every minute to see if the world was alive and reset the interface. >It's at the end of this message. It worked for me, but YMMV. Yes, it's a bug in the early chips - supposedly fixed in later steppings. The "official" workaround for the defect is to do what you're doing, but in the driver. Basically, if you don't see any packets come in over a period of a few seconds, then reset the card (actually, reprogram the multicast filter, but this requires re-initializing the card). I thought this was disgusting so I never implemented it. Sigh. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project