3c59x timeout problem

[Seva]

But I am running 2.2.6 ;)

So it's not limited to 2.0.36 - 2.2.2.

What's odd is that it happens with 3c595-T4 as well as 3c590!

/Simon

-- 
seva@seva.chicago.il.us
http://seva.chicago.il.us

On Tue, 27 Apr 1999, Jonathan Bartlett wrote:

> Date: Tue, 27 Apr 1999 19:44:52 -0500 (CDT)
> From: Jonathan Bartlett <johnnyb@janickelectronics.com>
> To: Seva <seva@null.cc.uic.edu>
> Cc: linux-vortex-bug@beowulf.gsfc.nasa.gov
> Subject: Re: 3c59x timeout problem
> 
> I used to have the same problem, although it would happen with almost no
> load at all.  I was communicating with a Windows machine using
> peer-to-peer wiring (i.e. no hub).  I never figured out the problem, but
> it stopped being a problem somewhere around 2.2.3.  It was a problem
> between 2.0.36 and 2.2.2 (I think).  Anywayy, hope that helps someone.
> 
> Jonathan Bartlett
> 
> On Tue, 27 Apr 1999, Seva wrote:
> 
> > 3c59x.c: 0.99H
> > Linux Kernek: 2.2.6
> > 
> > eth0: 3Com 3c590 Vortex 10Mpbs at 0xef20,  00:a0:24:8b:ad:a1, IRQ 10
> >   8K byte-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface.
> > 
> > I am sorry if this is inapropriate, but I have this problem with 3c590,
> > everyonce in a while, under heavy load, it just stops working and keeps on
> > spitting out:
> > 
> > eth0: transmit timed out, tx_status 00 status e000.
> > 
> > If I `ifdown eth0`, `rmmod 3c59x`, `ifup eth0`, it works again.
> > 
> > Any suggestions?
> > 
> > /Simon
> > 
> > -- 
> > seva@seva.chicago.il.us
> > http://seva.chicago.il.us
> > 
> > 
>