[eepro100] eepro100 driver frequently dying in Linux 2.4.4
mlists@barkley.garen.net
mlists@barkley.garen.net
19 May 2001 02:31:07 -0000
After upgrading from 2.2.18 to 2.4.4, my eepro card (Pro/100+ Management Adapter)dies after moderate use every other day. In /var/log/messages, I see stuff like this:
May 18 11:05:07 borgy kernel: NETDEV WATCHDOG: eth0: transmit timed out
May 18 11:05:07 borgy kernel: eth0: Transmit timed out: status f048 0c00 at 1646444/1646472 command 000ca000.
May 18 11:05:07 borgy kernel: eth0: Tx ring dump, Tx queue 1646472 / 1646444:
May 18 11:05:07 borgy kernel: eth0: 0 200ca000.
May 18 11:05:07 borgy kernel: eth0: 1 000ca000.
May 18 11:05:07 borgy kernel: eth0: 2 000ca000.
May 18 11:05:07 borgy kernel: eth0: 3 000ca000.
May 18 11:05:07 borgy kernel: eth0: 4 000ca000.
May 18 11:05:07 borgy kernel: eth0: 5 000ca000.
May 18 11:05:07 borgy kernel: eth0: 6 000ca000.
May 18 11:05:07 borgy kernel: eth0: 7 400ca000.
May 18 11:05:07 borgy kernel: eth0: = 8 200ca000.
May 18 11:05:07 borgy kernel: eth0: 9 000ca000.
May 18 11:05:07 borgy kernel: eth0: 10 000ca000.
May 18 11:05:07 borgy kernel: eth0: 11 000ca000.
May 18 11:05:07 borgy kernel: eth0: * 12 000ca000.
May 18 11:05:07 borgy kernel: eth0: 13 000ca000.
May 18 11:05:07 borgy kernel: eth0: 14 000ca000.
May 18 11:05:07 borgy kernel: eth0: 15 000ca000.
May 18 11:05:07 borgy kernel: eth0: 16 200ca000.
May 18 11:05:07 borgy kernel: eth0: 17 000ca000.
May 18 11:05:07 borgy kernel: eth0: 18 000ca000.
May 18 11:05:07 borgy kernel: eth0: 19 000ca000.
May 18 11:05:07 borgy kernel: eth0: 20 000ca000.
May 18 11:05:07 borgy kernel: eth0: 21 000ca000.
May 18 11:05:07 borgy kernel: eth0: 22 000ca000.
May 18 11:05:07 borgy kernel: eth0: 23 000ca000.
May 18 11:05:07 borgy kernel: eth0: 24 200ca000.
May 18 11:05:07 borgy kernel: eth0: 25 000ca000.
May 18 11:05:07 borgy kernel: eth0: 26 000ca000.
May 18 11:05:07 borgy kernel: eth0: 27 000ca000.
May 18 11:05:07 borgy kernel: eth0: 28 000ca000.
May 18 11:05:07 borgy kernel: eth0: 29 000ca000.
May 18 11:05:07 borgy kernel: eth0: 30 000ca000.
May 18 11:05:07 borgy kernel: eth0: 31 000ca000.
May 18 11:05:07 borgy kernel: eth0: Printing Rx ring (next to receive into 1709490, dirty index 1709490, dirty index 1709490).
May 18 11:05:07 borgy kernel: eth0: 0 0000a020.
May 18 11:05:07 borgy kernel: eth0: 1 0000a020.
May 18 11:05:07 borgy kernel: eth0: 2 0000a020.
May 18 11:05:07 borgy kernel: eth0: 3 0000a020.
May 18 11:05:07 borgy kernel: eth0: 4 0000a020.
May 18 11:05:07 borgy kernel: eth0: 5 0000a020.
May 18 11:05:07 borgy kernel: eth0: 6 0000a020.
May 18 11:05:07 borgy kernel: eth0: 7 0000a020.
May 18 11:05:07 borgy kernel: eth0: 8 0000a020.
May 18 11:05:07 borgy kernel: eth0: 9 0000a020.
May 18 11:05:07 borgy kernel: eth0: 10 0000a020.
May 18 11:05:07 borgy kernel: eth0: 11 0000a020.
May 18 11:05:07 borgy kernel: eth0: 12 0000a020.
May 18 11:05:07 borgy kernel: eth0: 13 0000a020.
May 18 11:05:07 borgy kernel: eth0: 14 0000a020.
May 18 11:05:07 borgy kernel: eth0: 15 0000a020.
May 18 11:05:07 borgy kernel: eth0: 16 0000a020.
May 18 11:05:07 borgy kernel: eth0: l 17 c000a022.
May 18 11:05:07 borgy kernel: eth0: *=18 0000a020.
May 18 11:05:07 borgy kernel: eth0: 19 0000a020.
May 18 11:05:07 borgy kernel: eth0: 20 0000a020.
May 18 11:05:07 borgy kernel: eth0: 21 0000a020.
May 18 11:05:07 borgy kernel: eth0: 22 0000a020.
May 18 11:05:07 borgy kernel: eth0: 23 0000a020.
May 18 11:05:07 borgy kernel: eth0: 24 0000a020.
May 18 11:05:07 borgy kernel: eth0: 25 0000a020.
May 18 11:05:07 borgy kernel: eth0: 26 0000a020.
May 18 11:05:07 borgy kernel: eth0: 27 0000a020.
May 18 11:05:07 borgy kernel: eth0: 28 0000a020.
May 18 11:05:07 borgy kernel: eth0: 29 0000a020.
May 18 11:05:07 borgy kernel: eth0: 30 0000a020.
May 18 11:05:07 borgy kernel: eth0: 31 0000a020.
After it does that about 3 or 4 times, networking with the card just fails altogether. If it helps, my setup looks like: Abit BP6 (Dual Celerons, ACPI v1.4), 768MB ram, serial# of card is 721383-810. I've just installed Intel's driver for the card v1.65 and it has been running fine for a few hours now, will see if it lasts. Any input welcome.
-Garen