MGBE - 10Gb Ethernet failure - "failed to get pcs block lock"

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

Hello,

We are using the AGX Orin Industrial on our custom board running jetPack 6.1 (r36.4). We are trying to establish link on 10Gb Ethernet to the MV1548 “Ironman” switch by Marvell, found on our custom board.
We followed the instruction on the “Jetson AGX Orin platform adaptation and Bring-up” document and the developer guide, and defined the interface as 10G XFI.

During boot, we get the following failure: “nvethernet 6800000.ethernet: [xpcs_lane_bring_up][470][type:0x4][loga-0x0] Failed to get PCS block lock”.

In ifconfig we can see the interface, and even if we restart it using ethtool we get the same failure message.

Moreover, we get “INIT” status from Marvell switch side and can’t reach “link-up” status.
The Switch is working properly, and we can see other links up.

Please see our dmesg output and DT node of the relevant Ethernet interface.
dmesg.txt (60.9 KB)
dt.txt (3.8 KB)

What could be the reason for this failure?

Thank you.

2

*** Please note that this reply is generated by LLM automatically ***

The issue you’re experiencing with establishing a 10Gb Ethernet link on your custom board with the Jetson AGX Orin Industrial module running JetPack 6.1 (r364) to the MV1548 Ironman switch by Marvell seems to be related to the configuration or compatibility of the Ethernet interface. Let’s break down the key points and potential reasons for the failure:

  1. PCS Block Lock Failure: The error message “Failed to get PCS block lock” indicates an issue with the Physical Coding Sublayer (PCS) block, which is part of the Ethernet PHY (Physical Layer). This could be due to a configuration mismatch or a hardware issue.

  2. Interface Configuration: You’ve defined the interface as 10G XFI (10 Gigabit XFI - a type of 10GbE interface). Ensure that this configuration matches the capabilities and settings of both the Jetson AGX Orin module and the Marvell switch. XFI is a specific type of 10GbE interface, and compatibility issues might arise if the switch or the module does not support it or if there’s a mismatch in the configuration.

  3. INIT Status from Marvell Switch: The fact that you’re getting an INIT status from the Marvell switch side and can’t reach linkup status suggests that there’s a problem with the link initialization. This could be due to a variety of reasons including cable issues, incorrect configuration, or incompatibility between the module and the switch.

  4. Comparison with Other Links: Since you mentioned that other links are up and working properly, it suggests that the issue is specific to this particular configuration or setup involving the Jetson AGX Orin module and the Marvell switch.

  5. dmesg Output and DT Node: The provided dmesg output and DT (Device Tree) node for the relevant Ethernet interface would offer more specific details about the failure. However, without access to these files, it’s challenging to provide a more precise diagnosis.

Given these considerations, here are some potential steps to resolve the issue:

  • Verify Configuration: Double-check the configuration of the Ethernet interface on both the Jetson AGX Orin module and the Marvell switch to ensure they match and are correctly set for 10G XFI.

  • Check Compatibility: Confirm that both the Jetson AGX Orin module and the Marvell switch support 10G XFI and that there are no known compatibility issues.

  • Cable and Connection: Ensure that the Ethernet cable and connections are good and not causing any issues.

  • Firmware and Software Updates: Make sure that both the Jetson AGX Orin module’s firmware and the Marvell switch’s firmware are up to date, as updates might resolve compatibility or configuration issues.

  • Consult Documentation and Support: Refer to the detailed documentation of both the Jetson AGX Orin platform and the Marvell switch for specific configuration guidelines and reach out to NVIDIA and Marvell support for further assistance if needed.

By systematically addressing these potential causes and taking the necessary steps, you should be able to identify and resolve the issue preventing the establishment of a 10Gb Ethernet link.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

1 Like
4

hello gilad.sokol,

it may due to configuration issues according to the logs,
for instance,

[   10.717183] nvethernet 6800000.ethernet: failed to read skip mac reset flag, default 0
[   10.717188] nvethernet 6800000.ethernet: failed to read MDIO address
[   10.717195] nvethernet 6800000.ethernet: setting to default DMA bit mask
[   10.723339] nvethernet 6800000.ethernet: failed to get phy reset gpio error: -2
[   10.733409] nvethernet 6800000.ethernet: Ethernet MAC address: 48:b0:2d:f1:21:a3
[   10.765479] nvethernet 6800000.ethernet: macsec parameter is missing or disabled
[   10.765483] nvethernet 6800000.ethernet: Macsec not supported/Not enabled
[   10.774786] nvethernet 6800000.ethernet: eth0 (HW ver: 31) created with 10 DMA channels

BTW,
please see-also Topic 298679 to enable Ethernet switch for reference.

6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.