eepro100 troubles

From: Scott R. Every (scott@emji.net)
Date: Wed Jun 07 2000 - 20:14:26 EST


I have a machine using this card and driver:
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/driv
ers/eepro100.html
eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V.
Savochkin <s
aw@saw.sw.com.sg> and others
eth0: Intel PCI EtherExpress Pro100 82557, 00:90:27:8D:36:FA, IRQ 21.
  Board assembly 000000-000, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).
  Receiver lock-up workaround activated.

The problem is my machine keeps dying after a day or so of fairly heavy net
traffic. using 2.2.15. It was rock solid until i put network load on it.
it was doing HEAVY processing before, but light net load with no trouble.
It seems the card is locking up, but there are no errors in messages or
syslog.
Is there any way to put this card into debug mode?
do you have any idea why its dying?

When it restarts i get a bunch of these:
eepro100: wait_for_cmd_done timeout!

then this:
eth0: Transmit timed out: status 0000 0c90 at 0/31 command 0001a000.
eth0: Tx ring dump, Tx queue 31 / 0:
eth0: * 0 0001a000.
eth0: 1 00020000.
eth0: 2 00030000.
eth0: 3 00030000.
eth0: 4 00030000.
eth0: 5 00030000.
eth0: 6 00030000.
eth0: 7 00030000.
eth0: 8 200c0000.
eth0: 9 000c0000.
eth0: 10 00030000.
eth0: 11 000c0000.
eth0: 12 00030000.
eth0: 13 000c0000.
eth0: 14 00030000.
eth0: 15 000c0000.
eth0: 16 200c0000.
eth0: 17 00030000.
eth0: 18 00030000.
eth0: 19 000c0000.
eth0: 20 000c0000.
eth0: 21 00030000.
eth0: 22 000c0000.
eth0: 23 00030000.
eth0: 24 200c0000.
eth0: 25 00030000.
eth0: 26 000c0000.
eth0: 27 000c0000.
eth0: 28 00030000.
eth0: 29 00030000.
eth0: 30 40030000.
eth0: =31 00000000.
eth0: Printing Rx ring (next to receive into 0, dirty index 0).
eth0: *= 0 00000001.
eth0: 1 00000001.
eth0: 2 00000001.
eth0: 3 00000001.
eth0: 4 00000001.
eth0: 5 00000001.
eth0: 6 00000001.
eth0: 7 00000001.
eth0: 8 00000001.
eth0: 9 00000001.
eth0: 10 00000001.
eth0: 11 00000001.
eth0: 12 00000001.
eth0: 13 00000001.
eth0: 14 00000001.
eth0: 15 00000001.
eth0: 16 00000001.
eth0: 17 00000001.
eth0: 18 00000001.
eth0: 19 00000001.
eth0: 20 00000001.
eth0: 21 00000001.
eth0: 22 00000001.
eth0: 23 00000001.
eth0: 24 00000001.
eth0: 25 00000001.
eth0: 26 00000001.
eth0: 27 00000001.
eth0: 28 00000001.
eth0: 29 00000001.
eth0: 30 00000001.
eth0: l 31 c0000002.

any idea what this means? i am starting to use intel cards for all my
servers and i am now very wary as this is causing huge problems on the
first server I've tried.

Any help would be appreciated.

thanx

s

--
Scott R. Every - mailto:scott@emji.net
EMJ Internet - http://www.emji.net
voice : 1-888-258-8959  fax : 1-919-363-4425
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu



This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:39 EST