[vortex-bug] Problems with 3c920, vortex and a 10baseT only router

[Donald Becker]

On Mon, 2 Dec 2002, Melchor Marín wrote:

> On Mon, 2 Dec 2002, Donald Becker wrote:
> >What driver version are you using?
...
> Dec  2 16:59:57 Quevedo kernel: 3c59x.c:v0.99Xf 11/17/2002 Donald Becker,
> becker@scyld.com
> Dec  2 16:59:57 Quevedo kernel:   http://www.scyld.com/network/vortex.html
> Dec  2 16:59:57 Quevedo kernel: eth0: 3Com 3c905C Tornado at 0xec80,
> 00:08:74:e2:cd:e0, IRQ 11
> Dec  2 16:59:57 Quevedo kernel:   8K buffer 5:3 Rx:Tx split,
> autoselect/Autonegotiate interface.
> Dec  2 16:59:57 Quevedo kernel:   MII transceiver found at address 24,
> status 7809.
> Dec  2 16:59:58 Quevedo kernel:   Using bus-master transmits and whole-frame
> receives.

That looks normal.

> Using vortex-diag -a shows:
> 
> [root@Quevedo mamarin]# vortex-diag -a
> vortex-diag.c:v2.12 11/27/2002 Donald Becker (becker@scyld.com)

Also all normal.

> >What are the error counts in /proc/net/dev?
> 
> Inter-|Receive                                                   |Transmit
>  face |bytes    packets errs drop fifo frame compressed multicast|bytes
> packets errs drop fifo colls carrier compressed
>     lo:       0       0    0    0    0     0          0         0        0
> 0    0    0    0     0       0          0
>   eth0:    2804      29    3    0    0     5          0         0     8434
> 88    0    0    0     0       4          0

This is bad -- you are getting CRC errors.  This typically means that
you have a bad cable.

What does 'mii-diag --watch' report as your pinging?


-- 
Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993