[247] in linux-net channel archive
Re: 3C503 quits responding to network
daemon@ATHENA.MIT.EDU (Andrew Howell)
Fri Apr 28 03:02:23 1995
From: andrew@kryten.it.com.au (Andrew Howell)
To: linux-net@vger.rutgers.edu
Date: Fri, 28 Apr 1995 13:06:02 +0800 (WST)
In-Reply-To: <Pine.LNX.3.91.950427194023.4068A-100000@ganderson-ppp.clark.net> from "Gary Anderson" at Apr 27, 95 08:52:37 pm
> Trying to troubleshoot a recently set up a 386/33 with Linux, kernel
> 1.2.4 (and 1.2.6), along with Paul Gortmaker's NE2000/8390 patches against
> 1.2.6, using a 3C503 for the interface. Problem is, and has been, that
> periodically the machine stops responding to the net. The machine itself
> doesn't lock up, it just goes deaf and won't even respond to pings. However,
> if we walk over to the console, do something on it _outbound_ to the net
> (e.g. - ping another machine) it begins responding to the net again. Have
> tried three different kernels, 1.2.1, 1.2.4, and now 1.2.6, as I said. The
> temporary solution we've adopted is to have cron ping another machine every 5
> minutes, but this is obviously a kludge. And even with a ping every 5
> minutes, sometimes the machine will still stop responding, and we must wait
> till the next ping for it to start responding again. One further bit of info
> - the ifconfig stats show dropped packets after this happens.
> Here is what shows up in the syslog:
> Apr 27 13:21:31 garc kernel: eth0: transmit timed out, TX status 0x0, ISR 0x0.
> Apr 27 13:21:31 garc kernel: eth0: Possible network cable problem?
> Any pointers about where the problem is would be greatly appreciated.
I'm getting this exact same problem. Things sending to the card lock up
until I send something out of it. It only started happening after I
got a new motherboard which forces me to only have 4 meg of RAM for a
bit. Maybe it's induced by low amount of ram? It nevered happened before
when I had 8 meg.
Andrew
-----------------------------------------------------------------------
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%. Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
-- Kryten in Red Dwarf `The Last Day'
Andrew Howell andrew@it.com.au
Perth, Western Australia howellaa@cs.curtin.edu.au
