It happends aproximatelly once in 2-3 months, I just usually
just 'ifconfing eth0 {down,up}' and things seems be back to normal.
eth0 Link encap:10Mbps Ethernet HWaddr 00:A0:24:6B:3B:D3
inet addr:x.x.x.x Bcast:x.x.x.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8833512 errors:0 dropped:0 overruns:0
TX packets:1911159 errors:0 dropped:0 overruns:0
Interrupt:10 Base address:0x6400
3c59x.c:v0.47 11/13/97 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html loading device 'eth0'...
eth0: 3Com 3c590 Vortex 10Mbps at 0x6400, 00:a0:24:6b:3b:d3, IRQ 10 32K byte-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface.
eth0: Overriding PCI latency timer (CFLT) setting of 32, new value is 248.
3c503.c: Presently autoprobing (not recommended) for a single card. loading device 'eth1'...
3c503.c:v1.10 9/23/93 Donald Becker (becker@cesdis.gsfc.nasa.gov)
eth1: 3c503 at i/o base 0x300, node 02 60 8c 4d 3a 60, using internal xcvr.
eth1: 3c503 - 8kB RAM, 8kB shared mem window at 0xdc000-0xddfff.
On Sun, 3 May 1998, Chris Evans wrote:
->Almost a week of uptime and I was at the console when suddenly I got lots
->of
->eth0: transmit timed out, tx_status 00, status e000
->And transmits were indeed dead. Who knows maybe the card would have
->recovered but as I was at the console I ifconfig'ed the card down and up,
->which restored networking properly.
->
->The card is a 3c590 8k Vortex
-Adam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu