eth0 tulip death

Chris Evans (chris@ferret.lmh.ox.ac.uk)
Mon, 9 Feb 1998 20:17:07 +0000 (GMT)


Hi,

Got into the lab this morning (well afternoon) and the networking was
dead on my workstation box. I believe it is running somthing like
2.0.31pre10.

tulip.c:v0.79 9/3/97 becker@cesdis.gsfc.nasa.gov
eth0: DEC DS21041 Tulip at 0x6000, 21041 mode, 00 c0 f0 14 7b ae, IRQ 11.
The following verbose information is emitted for
bug reports on media selection.
eth0:21041 Media information at 30, default media 0800 (Autosense).
eth0: 21041 media 00 (10baseT), csr13 0401 csr14 0000 csr15 0000.
eth0: 21041 media 00 (10baseT), csr13 0000 csr14 0000 csr15 0000.
eth0: 21041 media 00 (10baseT), csr13 0000 csr14 0000 csr15 0000.
eth0: Promiscuous mode enabled.
eth0: Promiscuous mode enabled.
eth0: No 21041 10baseT link beat, Media switched to 10base2.

<time passes>

eth0: 21041 transmit timed out, status fc260000, CSR12 000021c4, CSR13
ffffef09, CSR14 fffff7fd, resetting...

But alas the reset may well have not worked.

A rmmod/insmod pair on the tulip driver has got the thing going fine again
with no reboot.

As the machine is a workstation I'm not really bothered -- just in case
this hasn't been seen before.

If it _is_ a known problem and is fixed in a newer version of the tulip
driver, perhaps someone could post a brief summary?

Cheers
Chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu