[253] in linux-net channel archive
Re: 3C503 quits responding to network
daemon@ATHENA.MIT.EDU (Rob Janssen reading Linux mailingl)
Sat Apr 29 06:04:36 1995
To: ganderson@clark.net (Gary Anderson)
Date: Fri, 28 Apr 1995 10:04:30 +0200 (MET DST)
Cc: linux-net@vger.rutgers.edu, linux-kernel@vger.rutgers.edu,
paul@rasty.anu.edu.au
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
Reply-To: linux-vger@wab-tis.rabobank.nl
From: linux@sys3.pe1chl.ampr.org (Rob Janssen reading Linux mailinglist)
According to Gary Anderson:
> 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.
This is a problem not related to recent changes, it has been present for
a long time. It looks like it is related to the speed of the machine.
We have only seen it with an 8-bit 3c503 operating in a 386SX/20 machine.
When the same card was plugged into a 486DX/33 it never happened.
Indeed, fixes like you proposed (we have also used a continuous
ping with a long interval) solve the problem, but aren't very clean...
It looks like some timing problem. Probably something happens when the
driver does not pay attention to a certain event quickly enough?
Rob
--
+------------------------------------+--------------------------------------+
| Rob Janssen rob@knoware.nl | AMPRnet: rob@pe1chl.ampr.org |
| e-mail: pe1chl@wab-tis.rabobank.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU |
+------------------------------------+--------------------------------------+
