[FS#4032] Uplink ethernet ports not connecting at gigabit speeds (Ath79)

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#4032 - Uplink ethernet ports not connecting at gigabit speeds (Ath79)
User who did this - Boris Gjenero (dreamlayers)

----------
Yeah, I definitely have gigabit on the WAN port after installing openwrt-19.07.8-ar71xx-generic-wzr-600dhp-squashfs-sysupgrade.bin on my WZR-600DHP. Both ethtool and mii-tool say so, and the LED on the Arris TM822 cable modem is green instead of yellow.

    root at OpenWrt:~# ethtool eth1 | sed 's/^/    /'
    Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                             100baseT/Half 100baseT/Full 
                                             1000baseT/Full 
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 4
        Transceiver: internal
        Auto-negotiation: on
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: yes

Besides the speed differences, the "Transceiver" changed from "external" to "internal".

    root at OpenWrt:~# mii-tool -vvvv eth1 | sed 's/^/    /'
    Using SIOCGMIIPHY=0x8947
    eth1: negotiated 1000baseT-FD flow-control, link ok
      registers for MII PHY 4: 
        1000 796d 004d d041 01e1 c1e1 000d 2001
        0000 0200 3800 0000 0000 0000 0000 2000
        0862 bc50 0000 1000 002c 0000 0000 0000
        3200 0000 0000 0000 0000 0000 824e 0000
      product info: vendor 00:13:74, model 4 rev 1
      basic mode:   autonegotiation enabled
      basic status: autonegotiation complete, link ok
      capabilities: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
      advertising:  1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
      link partner: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD

dmesg also has lines confirming gigabit for both Ethernet interfaces:
    [   63.438575] eth0: link up (1000Mbps/Full duplex)
    [   67.947302] eth1: link up (1000Mbps/Full duplex)

I am able to use "ethtool -s eth1 speed 100 duplex full" and "ethtool -s eth1 speed 1000 duplex full" to change speed of eth0. The modem LED confirms the speed changes.

The dmesg changes might be relevant. This is from 19.07.8. It was interleaved with some other stuff. Weird how it says using port 4 as switch port and as PHY. But I guess they're two different devices, eth0 being ag71xx-mdio.0:00, eth1 being ag71xx-mdio.0:04.

    libphy: Fixed MDIO Bus: probed
    switch0: Atheros AR8316 rev. 1 switch registered on ag71xx-mdio.0
    ar8316: Using port 4 as switch port
    ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd041, driver=Atheros AR8216/AR8236/AR8316]
    eth0: Atheros AG71xx at 0xb9000000, irq 4, mode: rgmii
    ar8316: Using port 4 as PHY
    ag71xx ag71xx.1: connected to PHY at ag71xx-mdio.0:04 [uid=004dd041, driver=Atheros AR8216/AR8236/AR8316]
    eth1: Atheros AG71xx at 0xba000000, irq 5, mode: rgmii

This was from 21.02.0. Note how eth0 is changed to fixed, like the device tree says, with the Generic PHY driver. It doesn't seem like anything changed regarding eth1.

    libphy: Fixed MDIO Bus: probed
    libphy: ag71xx_mdio: probed
    switch0: Atheros AR8316 rev. 1 switch registered on mdio.0
    ag71xx 19000000.eth: connected to PHY at fixed-0:00 [uid=00000000, driver=Generic PHY]
    random: fast init done
    eth0: Atheros AG71xx at 0xb9000000, irq 4, mode: rgmii
    ar8316: Using port 4 as PHY
    ag71xx 1a000000.eth: connected to PHY at mdio.0:04 [uid=004dd041, driver=Atheros AR8216/AR8236/AR8316]
    eth1: Atheros AG71xx at 0xba000000, irq 5, mode: rgmii

It's weird how in 19.07.8 mii-tool claims eth0 is 100 Mbit. But ethtool and dmesg claim 1000, and I believe them. What is this anyways? I thought eth0 is connected directly to the switch chip, with no phy there.

    root at OpenWrt:~# mii-tool -vvvv eth0 | sed 's/^/    /'
    Using SIOCGMIIPHY=0x8947
    eth0: negotiated 100baseTx-FD flow-control, link ok
      registers for MII PHY 0: 
        1000 796d 004d d041 0de1 4d01 0005 2001
        0000 0200 1000 0000 0000 0000 0000 2000
        0862 7c1e 0000 1002 002c 0000 0000 0000
        3200 0000 0000 0000 0000 0000 02ee 0000
      product info: vendor 00:13:74, model 4 rev 1
      basic mode:   autonegotiation enabled
      basic status: autonegotiation complete, link ok
      capabilities: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
      advertising:  1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
      link partner: 100baseTx-FD flow-control

They don't seem swapped. Using mii-tool on eth0 affects LAN and eth1 affects WAN.

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4032#comment10186

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.