Sporadic messages in kernel log generated by MGBE interface

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

Dear NVIDIA Support,

We are using AGX Orin 64GB module on a custom board running JetPack 5.1.3 SDK with MGBE0 enabled.
The board routes the MGBE interface directly to SFP cage and the SFP transceiver is not installed however we continuously observe the following logs in the dmesg

[ 1570.839750] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1571.865751] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][470][type:0x4][loga-0x0] Failed to get PCS block lock

[ 1592.343747] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1593.369732] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][470][type:0x4][loga-0x0] Failed to get PCS block lock

[ 1599.511796] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1600.535797] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1601.559717] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1602.583720] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1603.607723] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1604.631718] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1605.657716] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][470][type:0x4][loga-0x0] Failed to get PCS block lock

[ 1609.751714] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

[ 1610.775713] nvethernet 6810000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

Upon reviewing the source code, we found that these messages appear due to the fact that the XPCS_WRAP_IRQ_STATUS register sets PCS_LINK_STS bit even though the link is down and no transceiver is installed.

Could you please provide documentation on the XPCS_WRAP_IRQ_STATUS register or any insights into why this behavior occurs?

Looking forward to your support.

5

Hi,

Optical transceivers/SFP is not tested or supported. Only XFI with a Ethernet PHY is tested and supported.

6

Dear Support,

We are seeing this bit assert even though no optical transceiver is populated, meaning the MGBE0 interface pins are floating so this not related to SFP/fiber use case.

What conditions could cause PCS_LINK_STS to become set when the MGBE0 pins are floating?

Also, please provide the description for the XPCS_WRAP_IRQ_STATUS register.

Thank you

7

@WayneWWW can we please have an update on this?