[ale] ethernet collisions/diag

[stephen]

On Sat, Oct 13, 2001 at 10:33:35AM -0700, Jim Popovitch wrote:
> Hi everyone,
> 
> I am having a high rate of collisions on a remote Cobalt Raq3i that I host a
> bunch of sites on.  Specifically this is what I am seeing (along w/ about 0 to
> 2% packet loss):
> 
> eth0 Link encap:Ethernet  HWaddr 00:10:E0:01:D1:B3
>      inet addr:209.132.85.174  Bcast:209.132.85.175  Mask:255.255.255.252
>      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>      RX packets:44736945 errors:0 dropped:0 overruns:0 frame:0
>      TX packets:49962335 errors:0 dropped:0 overruns:0 carrier:0
>      collisions:2495529 txqueuelen:100
>      Interrupt:11 Base address:0x1100
> 
> I recently d/l'ed an tried the Linux ethernet diag tool from:
> http://www.scyld.com/diag/.  I was unsuccessful in getting any data from the
> adapter (eepro100).  Here is the output from the eepro100-diag program:

I've never tried the driver specific diagnostic utilities, but you might want
to try the generic mii-diag utility (ftp://ftp.scyld.com/pub/diag/mii-diag.c).
It works find for me right now with the tulip driver.  And I've had success
with it before on the eepro100 driver.

> 
>   --------------------------------------------
>   root at blip~$ ./eepro100-diag -f -a
>   eepro100-diag.c:v2.05 6/13/2001 Donald Becker (becker at scyld.com)
>    http://www.scyld.com/diag/index.html
>   Index #1: Found a Intel 82559ER EtherExpressPro/100+ adapter at 0x1100.
>   i82557 chip registers at 0x1100:
>     0c000050 0f26c0e4 00000000 00080002 18050000 000000f0
>     No interrupt sources are pending.
>      The transmit unit state is 'Suspended'.
>      The receive unit state is 'Ready'.
>     This status is normal for an activated but idle interface.
>    The Command register has an unprocessed command 0c00(?!).
> 
>   root at blip~$ ./eepro100-diag -f -e
>   eepro100-diag.c:v2.05 6/13/2001 Donald Becker (becker at scyld.com)
>    http://www.scyld.com/diag/index.html
>   Index #1: Found a Intel 82559ER EtherExpressPro/100+ adapter at 0x1100.
>   Intel EtherExpress Pro 10/100 EEPROM contents:
>     Station address 00:10:E0:01:D1:B3.
>     Receiver lock-up bug exists. (The driver work-around *is* implemented.)
>     Board assembly 000000-000, Physical connectors present:
>     Primary interface chip None PHY #0.
>   --------------------------------------------
> 
> Is there another way to detect the driver settings (Full/Half, etc)?

Intel makes another linux driver for it NICs (e100) and I think it's GPL'd too.
At any rate, it's clean code and full of features (in the good sense).  I know
it allows you to query and configure a number of settings through entries in the
proc filesystem which includes link status.

stephen

> 
> What, if anything, can I do to debug and reduce the collisions?  Is the
> multicast setting possibly causing this? 
> 
> -Jim P.
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Make a great connection at Yahoo! Personals.
> http://personals.yahoo.com
> 
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
> sent to listmaster at ale dot org.
> 

---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.