[EMAIL PROTECTED] said:
> On Sat, 31 Jul 1999, Dave Wreski wrote:
>
> > Hi all. I just purchased an eepro100, and it's not performing as
well as
> > I expected. If I use 'ping -f remotehost' to a host on the same
subnet,
> > the hub collision light turns on solid, and percentage of packets
lost is
> > about 2% for 60k packets. Collisions are 25k from that it appears.
>
> > eth0: Intel PCI EtherExpress Pro100 at 0xef00, 00:90:27:8B:x:y, IRQ
10.
> > Receiver lock-up bug exists -- enabling work-around.
>
> This is an almost impossibly rare problem, it only occurs at 10Mbps.
> However, since the result is so severe (a complete reciever hang) the
driver
> monitors the receive traffic to avoid it. Reportedly only the oldest
chips
> have this bug, but the EEPROM hasn't been updated to indicate the fix.
Yes. I have experienced this before. On my side, the interfaces
sometimes
goes to "sleep". After a few minutes, people from my internal LAN
will not
be able to ping the interface. To enable back the interface, I need
to ping
from the problematic machine to which ever machine that cannot ping
that problematic machine.
My fix was to upgrade my kernel to 2.2.10. It has been very stable
ever since
and also significantly faster [os level].
Hope this helps.
Chris Shum
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
