2.2.10 & EtherExpress 16 "CU wedged, status 0040 0000"

Ben Armstrong (synrg@bgpc.dymaxion.ca)
Wed, 28 Jul 1999 09:17:57 -0300 (ADT)


Two nights ago, my nic locked up. In /var/log/messages I saw this:

Jul 27 00:53:01 sanctuary kernel: eth0: tx interrupt but no status

I get these all the time on two systems that use the eexpress 16. It
seems this is "normal" behaviour for this driver.

Jul 27 00:53:11 sanctuary kernel: eth0: CU wedged, status 0040 0000, resetting...
Jul 27 00:53:11 sanctuary kernel: eth0: i82586 reset timed out, kicking...
Jul 27 00:53:11 sanctuary last message repeated 4 times
Jul 27 00:53:11 sanctuary kernel: eth0: i82586 not responding, giving up.
Jul 27 00:53:21 sanctuary kernel: eth0: transmit timed out, board on fire?
<4>eth0: i82586 startup timed out, status 0040, resetting...
etc.

An ifconfig down, ifconfig up resolved the problem.

The card was only recently put in the machine. It had been running
fine under 2.2.10 for 5 days before this happened.

Any clues? Anything else I could check to help diagnose the problem?

Ben

--
    nSLUG       http://www.nslug.ns.ca      synrg@sanctuary.nslug.ns.ca
    Debian      http://www.debian.org       synrg@debian.org
    Chebucto    http://www.chebucto.ns.ca   aa458@chebucto.ns.ca
[ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0  1B B1 31 ED C6 A9 39 4F ]

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/