[tulip] overruns ?

[James Stevenson]

Hi

> On Thu, 17 Jan 2002, James Stevenson wrote:
>
> > > On Wed, 16 Jan 2002, James Stevenson wrote:
> > > > i have 2 cards from SMC each in 2 different computers and a 100mbps
> > switch
> > > > both work fine well almost in Full Duplex 100mbps.
> > >
> > > What is the detection message?
>
> What is the detection message?

Using the default interface 'eth0'.
Basic registers of MII PHY #1:  3000 786d 0022 5410 01e1 45e1 0005 2801.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx
10baseT-FD 10baseT, w/ 802.3X flow control.
   End of basic transceiver information.


> > > What does 'mii-diag' or 'tulip-diag -m' report?
> > not sure where can i get the utility ?
> > http://www.scyld.com  ?
>
> http://www.scyld.com/diag/index.html
>
> > > > eth0      Link encap:Ethernet  HWaddr 00:04:E2:1E:FE:B3
> > > >           RX packets:1339805 errors:356 dropped:0 overruns:356
frame:356
> > > >           TX packets:1403114 errors:0 dropped:0 overruns:0 carrier:0
> > > >           collisions:0 txqueuelen:100
> > >
> > > This could be a duplex mismatch.  If the link partner is not in full
> > > duplex mode, it will abort transmit on out-of-window collisions.  You
> > > will interpret that as receiving packets with CRC errors.
> > >
> > > There are other possibilities.  What does /proc/net/dev report?
> >
> >  face    bytes    packets     errs drop fifo frame compressed multicast
> > eth0    531841837 1702596      356    0  356   356          0        0
>
> This still looks pretty much like a duplex mismatch.