[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ethernet probs




I've gotten cloud233 patched up to 2.2.7 now - holy crap that's a big
difference.  I run some of my apps on my win98 box off of the NT domain
server (that's samba 2.something).  I thought it was reasonably fast before,
but damn, that's a big difference they made.  With teh 2.2.6 kernel I was
able to bring the network interface on cloud233 down in no time by just
transferring a bunch of files and causing colisions all over teh place
(hopfully the switch will take care of some of that too).  Tonight, I moved
about a gig of data between a couple of machines, including the win98 box,
saturating the network completely (which just wouldn't happen before).
Initially win 98 apps launched faster _with_ all the traffic than it did
before without the traffic, but then the windows box crashed.  This is good,
becuase windows is *supposed* to go down with the linux box still staying up
just fine.

In short, for my PPro with a 3c590, 2.2.7 is a very good thing.

On Sun, 25 Apr 1999, Cloudmaster wrote:

> 
> Apperantly, in the 2.2.7-pre3 patch, there's some workarounds for the slow
> windows connections, working around some of teh 'features' in the MS TCP
> stack.
> 
> --Danny, who thinks there's an awful lot of development going on in this
> stable kernel tree...
> 
> On Sun, 25 Apr 1999, Cloudmaster wrote:
> 
> > 
> > I've got a 3-com 3c590 (vortex) in my friendly PPro running kernel 2.2.6.
> > Whenever I try to send a lot of data out quickly (such as moving a few real
> > big files around my internal network), I get a whole slew of collisions and
> > eventually the card craps out, leaving messages such as this:
> > 
> > Apr 25 12:51:51 cloud233 kernel: eth0: Transmit error, Tx status register 90.
> > Apr 25 12:51:51 cloud233 kernel: eth0: Transmit error, Tx status register d0.
> > Apr 25 12:51:51 cloud233 kernel: eth0: Transmit error, Tx status register d0.
> > Apr 25 12:51:58 cloud233 kernel: eth0: transmit timed out, tx_status 00 status e 000.
> > 
> > and then it repeats that last line a few times, and all the network services
> > start dying and such as a result of the net going away.  Obviously, this
> > sucks.  As much as I'd like to bame this on the win98 machine on the network
> > (called "stain" for a reason), I think there may be some problem with the
> > linux end.  I also think that being on a hub rather than a switch
> > contributes, but I know that's not the whole problem.
> > 
> > Anyway, if you folks have any idea what may be causing this, I'd sure like
> > to hear it.  The mobile mp3 player will be wanting some files sent to it
> > pretty soon, and I don't wanna dissapoint it. :)
> > 
> > --Danny
> > 
> > 
> > --
> > To unsubscribe, send email to majordomo@luci.org with
> > "unsubscribe luci-discuss" in the body.
> > 
> 
> 
> --
> To unsubscribe, send email to majordomo@luci.org with
> "unsubscribe luci-discuss" in the body.
> 


--
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.