Hi
> The actual error would be useful. You have different kinds of overruns.
You
> could have your receive ring filling up faster than frames are being
pulled
> out (the 40% is meaningless...this occurs instantaneously and it only
takes
> 1 burst to do it)...or it could be an overrun on the card due to an
> inability to empty the fifo due to bus contention (adjusting the latency
> wont help much...if data is arriving to the NIC faster than it can empty
> its fifo, you will get an overrun). This could happen if you get a burst
of
> frames during a disk access...
that kind of lines up a bit with what i am seeing what i have is a few
486's with 10mbps card these work fine no problem even all 3 or so at once
but the other computer a cyrix P200 is 100mbps and you can even tell when
packets
are being dropped by watching the lights on the switch.
the machine i m having problems with is running nfs and a bust of traffic
which happens to be 8K or so of ip fragments from the nfs client @ 100mbps
though it works fine from the 486's 10mbps
the P200 also has a card of the same type in it and when idle no disk access
just nfs access and cat running will cause it to get the overruns as well
when
reading from an nfs mount.
> I would put some trace code in interrupt.c of the tulip driver...you'll
> notice that there are different kinds of errors...fifo errors, frame
errors
> etc...you need to know what you are getting to form a hypothesis.
i am not intirely to sure how todo this but i could probably do with the
documentation for the network card as well i dont suppose anyone would know
where i would be able to find this ?
thanks
James
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
