英伟达团队您好，在使用贵公司产品遇到了网络问题，在此请教一下思路！
模组类型：XavierNX 16GB；
系统版本：Ubuntu20.04 L4T: 35.4.1 （jetpack5.1.2）
使用网口为eth1：
Hi,
Please refer to
When running DeepStream, NETDEV WATCHDOG: eth0 (r8168): transmit queue 0 timed out - #6 by DaneLLL
This is known and would suggest upgrade. If you would like to stay on 5.1.2, please check the kernel code of 5.1.5 and do the porting.
感谢您的回复，我想再次和您确认一下，在jetpack5.1.5里面是不是彻底修复了这个问题，因为升级涉及的东西比较多，所以我们要确保彻底没有问题才能进行下一步升级动作。感谢！
Thank you for your reply. I would like to confirm with you again whether this issue has been completely fixed in jetpack 5.1.5. As the upgrade involves many things, we need to ensure that there are no problems before proceeding to the next upgrade action. thank!
Hi,
Yes, the fix is in Jetpack 5.1.5. You may upgrade to the version. Or manually merge the commits to previous version:
r8168: update driver to 8.053.00
r8168: Change file permissions of source files
r8168: Fix -20C 10mbps failure in Mods test
r8168: Disable 10M EEE
You can download kernel source of 5.1.5 by running source_sync.sh. And the commits are in kernel/nvidia
Thank you for your support!
We have upgraded the network card driver (r8168) for the existing Jetpack 5.1.2 environment, but the previous error still occurred during operation. So, may I ask where the problem lies?
Hi,
We would suggest add some prints in the driver code to make sure you are loading correct ko file. The path is changed so probably it does not load the correct ko file.
Hello, we have upgraded the network card driver for Jetpack 5.1.2 according to the plan you provided, but the previous error still occurred in the end. So I want to confirm two points with you: first, whether upgrading the network card driver in Jetpack 5.1.2 version can solve this problem; Secondly, if the Jetpack version is upgraded to 5.1.5, will this issue be completely resolved? Or is it true that after upgrading to the Jetpack version, users who have encountered the same issue have completely resolved the problem? I want to get a real and accurate answer, which is important for me to take the next action. Thank you for your reply!
Hi,
The patches are from vendor and supposed to fix the issue. If the issue persists, please consult with the vendor and see if there are later patches.
The Jetson Xavier NX integrates a Realtek RTL8211FDI Gigabit Ethernet controller. Do you observe the issue if you use this interface?
Hello, I didn’t understand what you meant by the following paragraph. We are using OrinNX, not Xavier NX.
The Jetson Xavier NX integrates a Realtek RTL8211FDI Gigabit Ethernet controller. Do you observe the issue if you use this interface?
Hi,
Your first comment says XavierNX 16GB. It is a bit confusing.
If you use Orin NX, we would suggest use Jetpack 6.2 instead of Jetpack 5.
Hello, sorry, I just checked the comments and it’s true that I made a mistake. The type of mod we are using is: OrinNX 16GB。 So what I want to confirm again is, if we solve this problem by upgrading Jetpack version, which version should we upgrade to, 5.1.5 or 6?
Hi,
The patches are in Jetpack 5.1.5 and 6.1 and later versions. We would suggest check it on Orin NX developer kit(Orin NX module + Orin Nano carrier board) to compare the test result on developer kit and your custom board. To confirm whether the issue is specific to using the custom board or not.
At present, we have recompiled the r8168.ko driver based on the r8168 network card source code of the Jetpack5.1.5 kernel source code in the orin nx + jetpack5.1.2 environment, and updated it to the current orin nx + jetpack5.1.2 environment. The problem still exists. Is there a patch for the r8168 driver for Jetpack 5.1.2?
Is it true that the patches related to r8168 are only applicable to Jetpack 5.1.5 and not to Jetpack 5.1.2?
Hi,
We don’t validate the patches on 5.1.2, so uncertain whether it completely fixes the issue on the version. Suggest you run your use-case on Orin NX developer kit(Orin NX module + Orin Nano carrier board) with 5.1.5 to confirm it works well first. Developer kit is the reference design and would suggest validating the use-case on the setup.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
