We encountered an issue while testing the nveth network card on OrinX:
Mar 04 05:56:22 orin kernel: nvethernet 6800000.ethernet: Failed to report error: reporter ID: 0x0, Error code: 0x1002, return: -19
Mar 04 05:56:28 orin kernel: nvethernet 6800000.ethernet: Failed to report error: reporter ID: 0x0, Error code: 0x1002, return: -19
Mar 04 05:57:27 orin kernel: nvethernet 6800000.ethernet: Failed to report error: reporter ID: 0x0, Error code: 0x1002, return: -19
Mar 04 05:57:30 orin kernel: nvethernet 6800000.ethernet: Failed to report error: reporter ID: 0x0, Error code: 0x1002, return: -19
Mar 04 05:58:19 orin kernel: nvethernet 6800000.ethernet: Failed to report error: reporter ID: 0x0, Error code: 0x1002, return: -19
Mar 04 05:58:56 orin kernel: nvethernet 6800000.ethernet: Failed to report error: reporter ID: 0x0, Error code: 0x1002, return: -19
Mar 04 05:59:26 orin kernel: nvethernet 6800000.ethernet: Failed to report error: reporter ID: 0x0, Error code: 0x1002, return: -19
We have identified that the error code corresponds to OSI_TX_FRAME_ERR. Could you clarify what specific issue this error indicates? Also, what does “Failed to report error” mean in this context?
Additionally, we found the definition of error code 0x1002 in the following file:
1.Looking forward to your guidance on the meaning of OSI_TX_FRAME_ERR ? 2.Looking forward to your guidance on the meaning why Failed to report errormessage.
Thank you for your reply. Yes, we are indeed designing our own custom base board. The basic functionality and performance of this network card are normal, including its features and stability. However, this error occasionally appears in the logs. We would like to understand the specific cause of this issue.
Thank you for your reply. We are using JetPack 36.3, and we discovered the issue during a bidirectional TCP bandwidth stability test with a 10G peer network using iperf3. I have already restarted the system and will try again to find a reliably reproducible scenario. Additionally, I will trace the specific assignment statement of the err variable in nvethernet.
Thank you very much for your suggestion! May I ask about the source of this patch and the related changelog? If we need to merge the patch into our own code, this information might be necessary.
You could check the same file on rel-35 and it will provide you the change log if you download the source code by using source_sync.sh. That one will have git logs.
This package contains the kernel source, and I found the modified version of the drivers/net/ethernet/nvidia/nvethernet/ether_linux.c file. However, I couldn’t locate the source_sync.sh script to retrieve the related Git information.
I’m a bit confused about how to obtain the nvethernet driver code with Git. Could you provide some guidance?
I downloaded the JetPack BSP package for version 35.6 from the official website. After extracting the kernel_src.tbz2(which does not include a Git repository), the directory structure looks like this:
➜ kernel ls
kernel-5.10 nvethernetrm nvgpu nvidia
I need the network driver located in ./nvidia/drivers/net/ethernet/nvidia/nvethernet/ether_linux.c. Then I found the official Git repository reference here:
However, after I cloned that repository, it only had the kernel-5.10 source with Git, and it did not include the nvidia folder that contains the nvethernet code.