Rx error: status 08 and 8c

[Nicholas J Kreucher]

hello again. i double checked my cables etc. i used a cable from a
100% working computer, and i even used that hub port too. still got the
crc errors. i then thought it might be something in the connector on
the card. so i turned off my computer (a rare thing!) and yanked the
3com card. everything looked ok... nothing seemed jammed in the Twisted
pair connector anywhere. i even put it back in a different PCI slot,
booted up, and still -- errors and bad pings.

On 08-Sep-99 Donald Becker wrote:
> 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.

ok, i checked it out and here it is:

Inter-|   Receive                                                | 
Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes
   packets errs drop fifo colls carrier compressed
    lo:   11393     164    0    0    0     0          0         0   
11393     164    0    0    0     0       0          0
  eth0:64502151  177569 3447    0    0  5181          0         0 
3557485   27270    0    0    0     0       0          0

sorry it looks kinda gumbled, but it's readable still... kinda. ;) i
guess the thing noticing is the Rx errors (and maybe frames too?)


>> 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.


hmmm ok makes sence...

 
>> 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.

ok... i reloaded the module with no options now...

have any other ideas? i am afraid my card might be going bad... i
bought this card because i thought it would last longer than any of the
el-cheapo brands. (about a year old now) kinda sad if it does turn out
to be bad...

pings are around 10% loss at the time of my writing this...

thanks again.

        - nick