[eepro100] eepro100 driver state

Jose Celestino japc@co.sapo.pt
Tue Mar 5 11:33:00 2002


I, how is the eepro100 driver in stability terms.

The question comes after I had a problem with our local gw. After a few
days of uptime we got without connectivity, dmesg displayed several:

NETDEV WATCHDOG: eth2: transmit timed out
eth2: Transmit timed out: status f088  0c00 at 7187202/7187232 command
0001a000.
eth2: Tx ring dump,  Tx queue 7187232 / 7187202:
eth2:   = 0 0003a000.
eth2:     1 4003a000.
eth2:  *  2 0001a000.
eth2:     3 0002a000.
eth2:     4 0003a000.
eth2:     5 000ca000.
eth2:     6 000ca000.
eth2:     7 000ca000.
eth2:     8 200ca000.
eth2:     9 0003a000.
eth2:    10 000ca000.
eth2:    11 000ca000.
eth2:    12 0003a000.
eth2:    13 000ca000.
eth2:    14 000ca000.
eth2:    15 0003a000.
eth2:    16 200ca000.
eth2:    17 000ca000.
eth2:    18 0003a000.
eth2:    19 000ca000.
eth2:    20 000ca000.
eth2:    21 0003a000.
eth2:    22 000ca000.
eth2:    23 000ca000.
eth2:    24 0003a000.
eth2:    25 000ca000.
eth2:    26 000ca000.
eth2:    27 0003a000.
eth2:    28 000ca000.
eth2:    29 000ca000.
eth2:    30 0003a000.
eth2:    31 4003a000.

And the interface didn't manage to recover with a simple ifconfig eth2
down; ifconfig eth2 up, I had to reboot.

What may be causing this? Solutions?

Kernel-2.4.18

3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:0c.0: 3Com PCI 3cSOHO100-TX Hurricane at 0x1080. Vers LK1.1.16
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@saw.sw.com.sg> and others
eth1: Intel Corp. 82557 [Ethernet Pro 100], 00:90:27:CB:B1:61, IRQ 11.
  Board assembly 721383-007, 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).
eth2: Intel Corp. 82557 [Ethernet Pro 100] (#2), 00:90:27:73:78:C2, IRQ
11.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly 677173-001, 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 (0x24c9f043).
  Receiver lock-up workaround activated.

TIA.

-- 
Jose Celestino <japc@co.sapo.pt> SysAdmin::SAPO.pt http://www.sapo.pt
---------------------------------------------------------------------
main(){printf("%xu%xk%x!\n",15,12,237);}