Rx error: status 08 and 8c

[Donald Becker]

On Wed, 8 Sep 1999, Nicholas J Kreucher wrote:

> hello... i am getting performance problems with my 3c905B card. pings
> are about 5-20% loss... and i get Rx errors in /sbin/ifconfig. i changed
> the debug for the module to 4 and the Rx error messages i get are:
> 
> Rx error: status 08
> Rx error: status 0c

You are getting CRC errors.
This should be reported in /proc/net/dev.

> i was looking though the mailing list archive and a suggestion for Rx
> errors for the 2.2.5-22 redhat 6.0 kernel was to add a route the main
> interface route with a window of 2048. i did this and the errors became
> less frequent, but pings were still pretty bad (~15%).

????
This will speed up retransmission, but it's just papering over the
underlying problem.  It won't help the packet loss rate.

> i tried a different cable, port etc and still no improvement. i tried a
> different computer (windows & different net card though) and pings were
> 100% using same port and cable.

Double check that.  CRC errors are usually the result of the cable or
connector.
(I'm assuming that you are using twisted pair.)

> i also tried putting full_duplex in 1 and 0, nothing really
> changed much between the two. also tried options=8, but nothing really
> changed much either...

Normally I would blame a duplex mismatch.
Never force full duplex unless you are talking to an ancient switch.

> /sbin/ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:10:4B:73:9B:0D  
>           RX packets:11615 errors:93 dropped:0 overruns:1 frame:148
>           TX packets:4921 errors:0 dropped:0 overruns:0 carrier:0

Use 'cat /proc/net/dev' for better numbers.

Donald Becker					  becker@cesdis.gsfc.nasa.gov
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771
301-286-0882	     http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html