DP83867IR: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

Hi Alexander,

Thanks for reaching out. Some questions to help isolate the issue:

• Which PHY + SoC are being used as the link partner?
• What is the output log for "ethtool -s eth0" ?
• Can the register dump be shared? Ethtool, mdio-tools, or phytool can help with this.
  • ethtool -d|--register-dump devname [raw on|off] [hex on|off]

Link failure is typically a PHY-level configuration issue, so I recommend confirming the configurations between [DP83867] and [Link Partner] are compatible, relative to:

• Auto-negotiation enabled / disabled
  
  • If disabled, are both PHYs set to force the same speed?
  • If enabled, do both PHYs advertise the same speeds? Register dump will confirm which advertisements were received remotely during auto-neg process.

Thank you,
Evan

Hi Evan,

- It's connected to a standard gigabit ethernet switch (NETGEAR Prosafe plus 8-port GS108E gigabit ethernet switch
- "ethtool -s eth0" returns no output
- sudo ethtool -d eth0 yields the following (from 0x0070 to 0x2ff0 is 0s). We are operating in Mode 1 (or at least intend to):

Offset          Values
------          ------
0x0000:         00 00 00 00 d7 20 00 10 28 84 16 78 0c 00 00 00
0x0010:         ff ff 00 d0 ff ff ff ff 00 00 00 00 00 00 00 20
0x0020:         07 06 07 07 1c 00 00 00 33 33 00 10 01 00 00 00
0x0030:         1c 00 00 00 00 01 00 10 01 00 00 5e 1c 00 00 00
0x0040:         00 01 00 10 fb 00 00 5e 00 00 00 00 00 00 00 00
0x0050:         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0060:         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0070:         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
...
0x2ff0:         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

- "ethtool eth0" yields the following:
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 10Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000000 (0)
        Link detected: no

We will also be testing if we are getting auto-negotiation pulses tomorrow as per the troubleshooting guide (https://www.ti.com/lit/an/snla246c/snla246c.pdf?ts=1770688800414&ref_url=https%253A%252F%252Fe2e.ti.com%252F).

Thank you for your help.

Hi Alexander,

Thanks for sharing. The format of this ethtool dump doesn't seem to correspond to 16bit readouts of each reg - can't confirm default constant PHYID values in 0x2/0x3. Please try phytool to read individual registers 0x0 - 0x1F:

https://github.com/wkz/phytool

[FAQ] How to read and write Ethernet PHY registers using a Linux terminal?

After validating register access, I recommend these checks:

• 0x1[2] to check link status
• 0x5 & 0x6 to verify if advertisements were received by link partner
  • Write 0x0[9] = '1' to restart auto-neg and check link status / advertisements received again
• If registers do not expect to intended configuration set by straps, read out registers 0x6E and 0x6F to confirm. May require extended method:

Thank you,
Evan