[LS2088ARDB] 10G copper port link state

[jhkim2]

Hi,

I have a problem of 10G copper port (dpmac.5, dpmac.6, dpmac.7, dpmac.8) link state of ls2088ardb.

After committing command "ls-addni dpmac.6", the netdevice eth0 is created.

I issued the command "ifconfig eth0 192.168.0.2 up" and the link state changed to "UP".

But, when I forced the link down with command "ifconfig eth0 down", the link goes to "Down" and after that the link state never goes to "UP" again as though I command "ifconfig eth0 up".

This problem happens in all copper ports in LS2088ardb and LX2160ardb also.

However, the problem seems not to happen in fiber ports(dpmac 1, 2, 3, 4 in ls2088 case).

How can I solve this problem?

Please give me hints.

Thanks.

[yipingwang · Accepted solution]

I used images from LSDK 21.08, didn't reproduce your problem, please refer to my following log.

root@TinyLinux:~# ls-listni
dprc.1/dpni.0 (interface: eth1, end point: dpmac.5)
root@TinyLinux:~# ls-addni dpmac.6
[ 45.544257] fsl_mc_allocator dpbp.1: Adding to iommu group 6
[ 45.551113] fsl_mc_allocator dpmcp.28: Adding to iommu group 6
[ 45.557669] fsl_mc_allocator dpcon.8: Adding to iommu group 6
[ 45.564061] fsl_mc_allocator dpcon.7: Adding to iommu group 6
[ 45.570464] fsl_mc_allocator dpcon.6: Adding to iommu group 6
[ 45.576848] fsl_mc_allocator dpcon.5: Adding to iommu group 6
[ 45.583241] fsl_mc_allocator dpcon.4: Adding to iommu group 6
[ 45.589623] fsl_mc_allocator dpcon.3: Adding to iommu group 6
[ 45.596017] fsl_mc_allocator dpcon.2: Adding to iommu group 6
[ 45.602408] fsl_mc_allocator dpcon.1: Adding to iommu group 6
[ 45.608801] fsl_dpaa2_eth dpni.1: Adding to iommu group 6
[ 45.715357] fsl_dpaa2_eth dpni.1 (unnamed net_device) (uninitialized): PHY [0x0000000008b97000:01] driver [Aquantia AQR405] (irq=POLL)
[ 45.727979] fsl_dpaa2_eth dpni.1: Probed interface eth2
Created interface: eth2 (object:dpni.1, endpoint: dpmac.6)
root@TinyLinux:~# ls-listni
dprc.1/dpni.1 (interface: eth2, end point: dpmac.6)
dprc.1/dpni.0 (interface: eth1, end point: dpmac.5)

root@TinyLinux:~# ifconfig eth2 192.168.0.2 up
[ 203.970435] fsl_dpaa2_eth dpni.1 eth2: configuring for phy/10gbase-r link mode
root@TinyLinux:~# [ 209.095930] fsl_dpaa2_eth dpni.1 eth2: Link is Up - 10Gbps/Full - flow control off
[ 209.103576] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready

root@TinyLinux:~# ./ethtool eth2
Settings for eth2:
Supported ports: [ ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: yes
root@TinyLinux:~# ifconfig eth2 down
[ 224.540921] fsl_dpaa2_eth dpni.1 eth2: Link is Down
root@TinyLinux:~# ./ethtool eth2
Settings for eth2:
Supported ports: [ ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: no
root@TinyLinux:~# ifconfig eth2 up
[ 239.138360] fsl_dpaa2_eth dpni.1 eth2: configuring for phy/10gbase-r link mode
[ 239.148623] fsl_dpaa2_eth dpni.1 eth2: Link is Up - 10Gbps/Full - flow control off
root@TinyLinux:~[ 239.156248] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
#
root@TinyLinux:~# ./ethtool eth2
Settings for eth2:
Supported ports: [ ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: yes
root@TinyLinux:~#

[jhkim2]

Thank you for support.

I tested with Linux kernel 4.19_rt in LSDK2004.

Following your test, I re-tested with Linux kernel 5.24 in LSDK2004 and the problems disappeared.

I think there are some differences in treating copper port link between the two linux kernel versions.