RX packet errors problem

[Swaine Lin Chen]

On Wed, 22 Mar 2000, Donald Becker wrote:

> On Wed, 22 Mar 2000, Swaine Lin Chen wrote:
> 
> > My problem is this: my eth0 interface gives me lots (up to 1%) of RX 
> > packet errors.  The card is a 3c590 10Mbit PCI adapter in a 200MHz PPro
> ..
> > slchen@vegas:~> /sbin/ifconfig
> > eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
> >           RX packets:103088 errors:205 dropped:205 overruns:0 frame:389
> >           TX packets:9057 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:2 txqueuelen:100 
> 
> Check /proc/net/dev for better stats.
> Hmmm, that's a very low collision number.  Verify that you haven't forced
> full duplex somehow.  That would explain Rx errors.
> 
> Or perhaps some other host is set to full duplex.  The usually, but not
> always, results in Tx errors rather than only Rx errors.
> 

First off, thanks for the quick response.  I'm impressed!

Full/half duplex isn't the problem, I think.  I got that vortex-diag
program, and it says I'm running half-duplex.  I've included the output
below.  I've also included the output of /proc/net/dev - to me, it just
seems to say the same thing...

Maybe I should ask a few more basic questions first - am I right in
viewing my RX packet errors as a problem?  Could this be causing the
relatively sluggish performance I see when using the network in Linux?  If
so, are there other culprits besides my configuration I should
consider?

One last really dumb questions - what is the "frame" number?  Is that an
error if it's not 0 as well?

Thanks again.


Swaine

-----------------------------------------
slchen@vegas:slchen/incoming# ./vortex-diag -a
vortex-diag.c:v1.09 7/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a 3Com 3c590 Vortex 10Mbps adapter at 0xff80.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 7, registers values by window:
  Window 0: 0000 0000 0000 0000 0000 00bf 0000 0000.
  Window 1: FIFO FIFO 0000 2000 8000 00ff 0ffc 2000.
  Window 2: 6000 6597 617c 0000 0000 0000 00de 4000.
  Window 3: 0010 0102 0000 0000 e138 0fff 0fff 6000.
  Window 4: 0000 00d0 0000 0e80 0000 98e0 0000 8000.
  Window 5: 1ffc 1ffc 00de 1ffc 0007 02de 00de a000.
  Window 6: 0000 0000 0000 6f00 0000 204f 229c c000.
  Window 7: 0000 0000 0000 0000 8000 00ff 0000 e000.
Vortex chip registers at 0xff80
  0xFF90: **FIFO** 00000000 00008000 *STATUS*
  0xFFA0: 00200008 0003c008 00200000 0003c808
  0xFFB0: ffffffff ffffffff ffffffff ffffffff
 Indication enable is 00de, interrupt enable is 02de.
 No interrupt sources are pending.
 Transceiver/media interfaces available:  10baseT 10base2 AUI.
Transceiver type in use:  10baseT.
 MAC settings: half-duplex.
Maximum packet size is 0.
 Station address set to 00:60:97:65:7c:61.
 Configuration options 4000.

slchen@vegas:slchen/incoming# more /proc/net/dev
Inter-|   Receive                                                |
Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes
packe
ts errs drop fifo colls carrier compressed
    lo:    4049      59    0    0    0     0          0         0     4049      
59    0    0    0     0       0          0
  eth0: 2856793   45338   56   56    0   104          0         0    71212
8
05    0    0    0     0       0          0

-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-vortex-bug-request@beowulf.org