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.
Note: the maximum hardware packet size is about 1480 payload bytes. Larger
packets are fragmented.
Are you getting any errors, especially Rx CRC or frame errors which indicate
a cable problem? Use 'cat /proc/net/dev' to check the error count.
You might want to check the link status with 'mii-diag'.
http://cesdis.gsfc.nasa.gov/linux/diag/index.html
> 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.
Donald Becker [EMAIL PROTECTED]
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center, Greenbelt, MD. 20771
301-286-0882 http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
