I can easily recreate the problem by running...
find /usr -type f -exec wc {} \;
while ping flooding the system. I have not tried this on kernel
version earlier then 2.1.127..
Boot messages, tulip driver is *not* a module.
tulip.c:v0.83 10/19/97 becker@cesdis.gsfc.nasa.gov
eth0: Digital DS21041 Tulip at 0x6100, 21041 mode, 00 c0 f0 21 72 0b, IRQ 9.
eth0:21041 Media information at 30, default media 0800 (Autosense).
eth0: 21041 media 00 (10baseT), csr13 0004 csr14 0000 csr15 0000.
eth0: 21041 media 00 (10baseT), csr13 0000 csr14 0000 csr15 0000.
Then I get the following errors (if transmit stops working) while
doing the ping flood and the above mentioned find.
eth0: 21041 transmit timed out, status fc660000, CSR12 000001c8, CSR13 ffffef05, CSR14 ffffff3f, resetting...
eth0: 21041 transmit timed out, status fc660010, CSR12 000052c8, CSR13 ffffef09, CSR14 fffff7fd, resetting...
eth0: 21041 transmit timed out, status fc660010, CSR12 000000c8, CSR13 ffffef05, CSR14 ffffff3f, resetting...
eth0: 21041 transmit timed out, status fc660010, CSR12 000050c8, CSR13 ffffef09, CSR14 fffff7fd, resetting...
eth0: 21041 transmit timed out, status fc660010, CSR12 000000c8, CSR13 ffffef05, CSR14 ffffff3f, resetting...
eth0: 21041 media switched to 10baseT.
eth0: 21041 transmit timed out, status fc660010, CSR12 000000c8, CSR13 ffffef05, CSR14 ffffff3f, resetting...
eth0: 21041 transmit timed out, status fc660010, CSR12 000050c8, CSR13 ffffef09, CSR14 fffff7fd, resetting...
ifconfig eth0 down; ifconfig eth0 up
fixes the problem.
If receive stops working, but transmit is still ok, I get no error messages.
System is a UP 200MHz K6, all SCSI, Kingston KNE40T tulip based
ethernet card.
Jim Bauer, jfbauer@home.com
-
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/