From owner-freebsd-hackers  Fri Sep 26 02:28:04 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA24300
          for hackers-outgoing; Fri, 26 Sep 1997 02:28:04 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA24236;
          Fri, 26 Sep 1997 02:27:56 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA22718;
	Fri, 26 Sep 1997 02:28:52 -0700 (PDT)
Message-Id: <199709260928.CAA22718@implode.root.com>
To: Ruslan Ermilov <ru@ucb.crimea.ua>
cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG
Subject: Re: your mail 
In-reply-to: Your message of "Fri, 26 Sep 1997 10:53:42 +0300."
             <199709260753.KAA01057@relay.ucb.crimea.ua> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 26 Sep 1997 02:28:52 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I'm using 3 EtherExpress cards:
>
>fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 2 int a irq 10 on pci0:10
>fxp0: Ethernet address 00:a0:c9:55:13:22
>fxp1 <Intel EtherExpress Pro 10/100B Ethernet> rev 1 int a irq 9 on pci0:12
>fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps
>fxp2 <Intel EtherExpress Pro 10/100B Ethernet> rev 1 int a irq 9 on pci0:14
>fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps
>
>Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently freezes.
>When I `ifconfig down delete fxp0' and then ifconfig it up, the situation
>resolves.

   If this is true, then Intel has apparantly lied to me about fixing the
problem in the "next stepping" of the chip. The lock up should only occur
when garbage bits occur in the preamble of a packet. It's not supposed to
happen in 100Mbps mode (only 10Mbps), but since I've personnally been able
to get it to happen in 100Mbps, I don't believe it. I can reproduce the
problem only under special circumstance like power-cycling the hub.
   You might try using the "link0 link1 -link2" flags on the 100Mbps link
to force it to stay in 100/half...this might prevent the lock up from
occuring (but I've not tested this myself).

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project