> > > eth0: transmit timed out, tx_status 88 status e000.
> > > eth0: Transmitter encountered 16 collisions -- network network cable problem?
>
> 16 collisions isnt an error - it just thinks your cable was very busy or fell
> out.
agreed. but after this "non-error" the driver is dead and needs ifconfig down/up...
> > Harald's test program "ntest" (reading data on one host from /dev/zero and
> > writing it on another machine to /dev/null) other network connections
> > dramatically slow down. A ftp session running concurrently to ntest gets
> > only 3KB/sec. "ifconfig eth0" does not show any errors or overruns.
>
> Ethernet isnt fair, ethernet isnt meant to be fair. Use token ring if you
> want fairness. That one isnt a bug (the comment above about 450K/sec clearly
> IS a bug tho)
yes, it's related to a (hardware or software) bug, too. as long as I'm using
drivers with good receive performace (6-7MB/sec), running two separate transfers
between four different PCs are scheduled almost 50/50. this massive "unfairness"
only shows up when read performace sucks anyway (but I'm very well aware that
ethernet can be completely unfair though)...
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^