Re: Problem with connection of EtherExpress Pro100 to a 10/100 switch

On Thursday 16 October 2003 17:31, Donald Becker wrote:
> Please don't sign messages to the lists:
>    they look like spam
>    I must manually moderate and check every email with an attachment
>    it doesn't do any good,
>    it results in ugly archives and digests

Ok.

> > I'm running linux 2.4.22 and recently moved from a longshine 8 port
> > 10/100 
 switch to a 16 port 10/100 switch also from longshine. I
> > reconnected all my rtl8139 based cards with no problems. I also
> > reconnected a EtherExpress Pro100 to it and it reports from mii-tool:
> > 
> > eth0: negotiated 100baseTx-FD flow-control, link ok
>
> 
> What does 'mii-diag' report?
> The 'mii-tool' program uses code from 'mii-diag', but there is a real
> reason why I wrote 'mii-diag' to produce the output that it does.

mii-diag -v output for the working card follows (this machine is running 
2.4.18 & eepro100.o version 1.36. I'm using the kernel included driver in all 
machines. But just to test i tried the e100.o driver & the problem is the 
same.):

mii-diag.c:v2.09 9/06/2003 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Using the default interface 'eth0'.
  Using the old SIOCGMIIPHY value on PHY 1 (BMCR 0x3000).
 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.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 
10baseT-FD 10baseT, w/ 802.3X flow control.
   End of basic transceiver information.

 MII PHY #1 transceiver registers:
   3000 782d 02a8 0150 05e1 45e1 0001 ffff
   ffff ffff ffff ffff ffff ffff ffff ffff
   0203 0000 0001 ffff 0000 0000 ffff 0000
   0174 0000 0000 0000 ffff ffff ffff ffff

> 
>
> > ... but when i reconnected my other EtherExpress Pro100 (this one is an 
> > onboard one), it apparently cant autonegotiate with the switch no matter
> > how 
 much time i give it. The only way to get link is forcing the speed
> > to 100BaseTx-FD. It works fine after that, desconnecting and reconnecting
> > the cable. Except, the problem comes back when i power off & on the
> > system.
>
> 
> If it works fine forced to full duplex, then the link partner is forced
> to full duplex.  Forcing speed or full duplex turns off autonegotiation,
> which explains what you are seeing.

But i didnt force the switch to full duplex in any way. I dont even know a way 
to do it. All other cards do autonegotiation ok.

> > These cards are on different machines. I'm using the kernel driver
> > eepro100.o
>
> 
> What driver version?
> Is there a reason the driver version was omitted from your message?

Just forgot. The non-working card is running the driver included in 2.4.22 
which is eepro100.o version 1.36. So they are both using the same version of 
the driver but different kernels.

> > This is the output of mii-diag -v on the non-working card (after i fixed
> > the 
 speed):
>
> What was it before you forced the speed (and thus disabled
> autonegotiation)?

Ok, i now restarted autonegotiation  and i have no link on the card & on the 
switch. This is the output of mii-diag -v in this state:

mii-diag.c:v2.09 9/06/2003 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Using the default interface 'eth0'.
  Using the new SIOCGMIIPHY value on PHY 1 (BMCR 0x1000).
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Your link partner is generating 100baseTx link beat  (no autonegotiation).
   End of basic transceiver information.

libmii.c:v2.10 4/22/2003  Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
 MII PHY #1 transceiver registers:
   1000 7809 02a8 0154 05e1 05e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0001 0000 0000 0000 0000 0000
   0000 0000 0b20 0000 0000 0000 0000 0000.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Vendor ID is 00:aa:00:--:--:--, model 21 rev. 4.
   Vendor/Part: Intel 82559 transceiver.
 I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 05e1: Flow-control 100baseTx-FD 100baseTx 
10baseT-FD 10baseT.
   Negotiation did not complete.
  Intel 8255* PHY #1 extended management registers:
    Error counts, cleared when read:
     False carriers 0
     Link disconnects 0
     Receive errors 0
     Rx symbol errors 0.
     Rx 10Mbps Early End-Of-Frame errors 0.
     Rx 100Mbps Early End-Of-Frame errors 0.
     Tx jabber errors 0.


> 
> The output of 'mii-diag --watch eth0', while re-plugging the cable, might
> be useful here. 

Here it is:

Using the default interface 'eth0'.
Basic registers of MII PHY #1:  1000 7809 02a8 0154 05e1 05e1 0001 0000.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
 Your link partner is generating 100baseTx link beat  (no autonegotiation).
   End of basic transceiver information.

Monitoring the MII transceiver status.
18:47:24.246  Baseline value of MII BMSR (basic mode status register) is 7809.


... Unplugging & replugging the cable while mii-diag is running causes no 
change. Connecting on other ports in the switch also produces no change. 
Also, how can my link partner be generating link beat when at that time the 
cable was disconnected ?

This is a very annoying problem.

Thanks
-- 
+-------------------------------------------------------------------------+
|PGP Public Key: http://sys49152.net/pubkey.asc                           |
+-------------------------------------------------------------------------+