Device direct connection network stuck

Hi,
I found that there was a network jam on two Jetson Xavier NX devices directly connected; This is the result of my two-way test using iperf tool:

device info:

$ jetson_release 
 - NVIDIA Jetson Xavier NX (Developer Kit Version)
   * Jetpack 4.6.1 [L4T 32.7.1]
   * NV Power Mode: MODE_20W_6CORE - Type: 8
   * jetson_stats.service: active
 - Libraries:
   * CUDA: 10.2.300
   * cuDNN: 8.2.1.32
   * TensorRT: 8.2.1.8
   * Visionworks: 1.6.0.501
   * OpenCV: 4.1.1 compiled CUDA: NO
   * VPI: ii libnvvpi1 1.2.3 arm64 NVIDIA Vision Programming Interface library
   * Vulkan: 1.2.70
$ sudo ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                             100baseT/Half 100baseT/Full 
                                             1000baseT/Full 
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Link detected: yes

one Jetson Xavier NX device(192.168.1.3):

iperf3 -s 
iperf3 -c 192.168.1.101 -p 5201 -t 100

another Jetson Xavier NX device(192.168.1.101):

iperf3 -s 
iperf3 -c 192.168.1.3 -p 5201 -n 445440000000

But no problem was found through the net switch connection.

Is it a well-known issue?

We never treid on two Jetson Xavier NX devices directly connected to do the test, not sure if it’s an issue. What’s the real use case for this test?

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