Re: 3C509 locks up consistantly

Yoink! (xombi@accessus.net)
Mon, 22 Nov 1999 15:36:19 -0600 (CST)


Unfortunately, mine doesn't respond to the module unload or a ifdown/ifup....
only a hardboot fixes it.

On 21 Nov 1999, Miquel van Smoorenburg wrote:
> In article <cistron.Pine.LNX.3.96.991121104202.27668A-100000@mtvernon1.accessus.net>,
> Yoink! <xombi@accessus.net> wrote:
> >I have a Red Hat linux 6.0 box (Celeron 433Mhz, not overclocked!, with
> >196M RAM and a IBM 6.4G IDE, on a Abit ZM6) on a remote network. Every 5
> >or so days, it used to lose eth0 (3c509) and no packets would come in or
> >out, despite the fact that the box was still up. Rebooting fixes the
> >problem, Rebooting every 3 or so days kept the problem from occuring at
> >all.
>
> FWIW, I have the same problem on our news server (averages 9 Mbit/sec
> in and 20 Mbit/sec out), with both eepro100 and epic100 cards.
> It now locks up every 2 hours. A script run by cron every two minutes
> detects this, shuts down the network, removes the driver module, reloads
> it, re-initializes the network and it's up again. The weird thing
> is that after a reboot, it runs for a day or so without problems, and
> then it starts locking more and more often up to like twelve times a day ..

-
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/