Hi Michael,
thx for your reply, here is the info you requested:
> 1. ethtool eth0 with a working kernel. I'd like to see the MDI-X
> setting when it is working.
root@XXXXXX ~ # cat ethtool_working_3.0.9
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
MDI-X: Unknown
Supports Wake-on: g
Wake-on: g
Current message level: 0x000000ff (255)
drv probe link timer ifdown ifup rx_err tx_err
Link detected: yes
> 2. mii-tool -vvv eth0 with the non-working kernel.
root@XXXXXX ~ # cat miitool_non_working_3.4.11
Using SIOCGMIIPHY=0x8947
eth1: 100 Mbit, full duplex, no link
registers for MII PHY 1:
2100 7949 0020 6340 0041 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 3000
0001 2000 0000 0000 0000 0000 0000 4000
7277 1000 0000 ffff 2801 0000 0000 0000
product info: vendor 00:08:18, model 52 rev 0
basic mode: 100 Mbit, full duplex
basic status: no link
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 10baseT-FD
What looks suspicious here is the last line of mii-tool output:
'advertising: 10baseT-FD', while only 100baseTx-FD is set on a switch.
'mii-tool -vvv eth1' on working 3.0.9 gives output like below:
root@XXX ~ # cat miitool_working_3.0.9
Using SIOCGMIIPHY=0x8947
eth1: 100 Mbit, full duplex, link ok
registers for MII PHY 1:
2100 794d 0020 6340 0501 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 3000
0001 0301 0000 0000 0000 0000 0000 4000
7277 0504 0000 ffff 2801 0000 0000 0000
product info: vendor 00:08:18, model 52 rev 0
basic mode: 100 Mbit, full duplex
basic status: link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD flow-control
Any ideas?
Regards,
Marcin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
