TX2 network card crash by connecting [InteL(R) I210/I211 Gigabit Network] with network cable connection

The PC with a InteL® I210/I211 Gigabit Network cark connect to the TX2, the TX2 network card will often crash with runing a few minutes or hours.When the TX2 network card crash ,the system is runing normally and the cmd of ethtool seem to be fun, however it can not ping the PC.
But if the PC and TX2 connect by a switch ,the problem can not be reproduced.
And the problem can not be reproduced with other models of network cards

The problem can reproduce by the methord:

TX2 ip:192.168.4.32

nvidia@nvidia-desktop:~$ head -n 1 /etc/nv_tegra_release
# R32 (release), REVISION: 2.3, GCID: 17644089, BOARD: t186ref, EABI: aarch64, DATE: Tue Nov  5 21:48:17 UTC 2019

PC(with InteL® I210/I211 Gigabit Network) ip:192.168.4.33

TX2 run the two command together:

iperf3 -s
iperf3 -c 192.168.4.33 -n 100G -P 4

PC(Windows) run the two command together:

iperf3.exe -s
iperf3.exe -c 192.168.4.32 -n 100G -P 4

How can I avoid the problem?
Thanks!

Before you start your test try to run “dmesg --follow” (this displays log lines as they occur). Take note of what the last log lines are, and then when things start failing, post what extra log lines appear.

“dmesg --follow” nothing update.

nvidia@nvidia-desktop:~$ dmesg --follow -T
[二 12月  3 10:03:43 2019] wifi_platform_get_mac_addr
[二 12月  3 10:03:43 2019] Firmware up: op_mode=0x0005, MAC=00:04:4b:c5:38:be
[二 12月  3 10:03:43 2019] clm path from default:/lib/firmware/brcm/bcmdhd.clm_blob
[二 12月  3 10:03:43 2019] Skipping the clm download. len:0 memblk:          (null)
[二 12月  3 10:03:43 2019] dhd_preinit_ioctls pspretend_threshold for HostAPD failed  -23
[二 12月  3 10:03:43 2019] Firmware version = wl0: May 17 2019 16:59:40 version 7.35.349.79 (r714996 CY) FWID 01-e527e2ad
[二 12月  3 10:03:43 2019] dhd_interworking_enable: failed to set WNM info, ret=-23
[二 12月  3 10:03:43 2019] CFGP2P-ERROR) wl_cfgp2p_add_p2p_disc_if : 
[二 12月  3 10:03:43 2019] P2P interface registered
[二 12月  3 10:03:43 2019] WLC_E_IF: NO_IF set, event Ignored
[二 12月  3 10:03:43 2019] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[二 12月  3 10:03:43 2019] tegra-xusb 3530000.xhci: entering ELPG
[二 12月  3 10:03:43 2019] tegra-xusb 3530000.xhci: entering ELPG done
[二 12月  3 10:03:44 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[二 12月  3 10:03:44 2019] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[二 12月  3 10:03:45 2019] l4tbr0: port 1(rndis0) entered blocking state
[二 12月  3 10:03:45 2019] l4tbr0: port 1(rndis0) entered forwarding state
[二 12月  3 10:03:45 2019] IPv6: ADDRCONF(NETDEV_UP): l4tbr0: link is not ready
[二 12月  3 10:03:45 2019] IPv6: ADDRCONF(NETDEV_CHANGE): l4tbr0: link becomes ready
[二 12月  3 10:03:52 2019] tegradc 15210000.nvdisplay: blank - powerdown
[二 12月  3 10:03:54 2019] fuse init (API version 7.26)
[二 12月  3 10:03:54 2019] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[二 12月  3 10:03:54 2019] Bluetooth: BNEP socket layer initialized
nvidia@nvidia-desktop:~$ date && iperf3 -c 192.168.1.67 -n 100G -P 4
2019年 12月 03日 星期二 10:05:17 CST
Connecting to host 192.168.1.67, port 5201
[  4] local 192.168.1.79 port 44978 connected to 192.168.1.67 port 5201
[  6] local 192.168.1.79 port 44980 connected to 192.168.1.67 port 5201
[  8] local 192.168.1.79 port 44982 connected to 192.168.1.67 port 5201
[ 10] local 192.168.1.79 port 44984 connected to 192.168.1.67 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  22.8 MBytes   190 Mbits/sec    0    211 KBytes       
[  6]   0.00-1.00   sec  27.9 MBytes   234 Mbits/sec    0    216 KBytes       
[  8]   0.00-1.00   sec  27.4 MBytes   229 Mbits/sec    0    223 KBytes       
[ 10]   0.00-1.00   sec  23.4 MBytes   196 Mbits/sec    0    218 KBytes       
[SUM]   0.00-1.00   sec   101 MBytes   849 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   1.00-2.01   sec  23.6 MBytes   197 Mbits/sec    3    147 KBytes       
[  6]   1.00-2.01   sec  24.7 MBytes   206 Mbits/sec    0    216 KBytes       
[  8]   1.00-2.01   sec  25.0 MBytes   208 Mbits/sec   23    157 KBytes       
[ 10]   1.00-2.01   sec  24.0 MBytes   200 Mbits/sec    0    218 KBytes       
[SUM]   1.00-2.01   sec  97.3 MBytes   810 Mbits/sec   26             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   2.01-3.00   sec  18.0 MBytes   152 Mbits/sec    0    185 KBytes       
[  6]   2.01-3.00   sec  24.5 MBytes   207 Mbits/sec    0    216 KBytes       
[  8]   2.01-3.00   sec  18.7 MBytes   158 Mbits/sec    0    194 KBytes       
[ 10]   2.01-3.00   sec  26.5 MBytes   224 Mbits/sec    0    218 KBytes       
[SUM]   2.01-3.00   sec  87.7 MBytes   741 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   3.00-4.00   sec  23.2 MBytes   195 Mbits/sec    0    211 KBytes       
[  6]   3.00-4.00   sec  24.0 MBytes   202 Mbits/sec    0    216 KBytes       
[  8]   3.00-4.00   sec  23.2 MBytes   196 Mbits/sec    0    212 KBytes       
[ 10]   3.00-4.00   sec  24.1 MBytes   203 Mbits/sec    0    218 KBytes       
[SUM]   3.00-4.00   sec  94.6 MBytes   796 Mbits/sec    0             
……………………
[  4]  51.00-52.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  6]  51.00-52.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  8]  51.00-52.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[ 10]  51.00-52.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[SUM]  51.00-52.00  sec  0.00 Bytes  0.00 bits/sec    4             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]  52.00-53.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  6]  52.00-53.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  8]  52.00-53.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[ 10]  52.00-53.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[SUM]  52.00-53.00  sec  0.00 Bytes  0.00 bits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]  53.00-54.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  6]  53.00-54.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  8]  53.00-54.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[ 10]  53.00-54.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[SUM]  53.00-54.00  sec  0.00 Bytes  0.00 bits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]  54.00-55.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  6]  54.00-55.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  8]  54.00-55.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[ 10]  54.00-55.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[SUM]  54.00-55.00  sec  0.00 Bytes  0.00 bits/sec    1             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]  55.00-56.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  6]  55.00-56.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  8]  55.00-56.00  sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[ 10]  55.00-56.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[SUM]  55.00-56.00  sec  0.00 Bytes  0.00 bits/sec    3             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]  56.00-56.94  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  6]  56.00-56.94  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  8]  56.00-56.94  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[ 10]  56.00-56.94  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[SUM]  56.00-56.94  sec  0.00 Bytes  0.00 bits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-56.94  sec  1.14 GBytes   172 Mbits/sec    8             sender
[  4]   0.00-56.94  sec  0.00 Bytes  0.00 bits/sec                  receiver
[  6]   0.00-56.94  sec  1.18 GBytes   179 Mbits/sec    5             sender
[  6]   0.00-56.94  sec  0.00 Bytes  0.00 bits/sec                  receiver
[  8]   0.00-56.94  sec  1.15 GBytes   174 Mbits/sec   28             sender
[  8]   0.00-56.94  sec  0.00 Bytes  0.00 bits/sec                  receiver
[ 10]   0.00-56.94  sec  1.19 GBytes   179 Mbits/sec    5             sender
[ 10]   0.00-56.94  sec  0.00 Bytes  0.00 bits/sec                  receiver
[SUM]   0.00-56.94  sec  4.66 GBytes   703 Mbits/sec   46             sender
[SUM]   0.00-56.94  sec  0.00 Bytes  0.00 bits/sec                  receiver
iperf3: interrupt - the client has terminated

“dmesg --follow” nothing update.

Does the rest of the system appear to run normally after the failure? I am wondering if a lack of dmesg logging might mean something else stopped working at the same time and prevented logging. It may be that with no message the network card’s driver did not actually crash, e.g., a switch might change something in a configuration. What follows assumes the driver itself did not fail, and that something else is going on (if dmesg did not display anything, and if dmesg appears to otherwise be behaving normally, then it is a safe bet that the NIC driver did not fail).

Because this does not crash with a switch, but has some random failure when not using the switch, can you say more about the cabling when not using the switch? Is this a crossover cable, and how long is it?

Prior to the test, are you using both the Intel NIC and the integrated NIC? What is the output of “ifconfig” both before and after the failure? Some of those statistics may indicate other network issues.

The length of the cabling is 1 meter, and cat6 crossover cable.
The test PC use both the Intel NIC and the integrated NIC.Intel I210 and Intel I219
before test.

nvidia@nvidia-desktop:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.79  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::204:4bff:fec5:38c0  prefixlen 64  scopeid 0x20<link>
        ether 00:04:4b:c5:38:c0  txqueuelen 1000  (Ethernet)
        RX packets 5260559  bytes 2314484941 (2.3 GB)
        RX errors 0  dropped 343548  overruns 0  frame 0
        TX packets 439290  bytes 3740279718 (3.7 GB)
        TX errors 1006  dropped 0 overruns 0  carrier 1006  collisions 0
        device interrupt 41

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 198275  bytes 16705307 (16.7 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 198275  bytes 16705307 (16.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:04:4b:c5:38:be  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

after test

nvidia@nvidia-desktop:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.79  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::204:4bff:fec5:38c0  prefixlen 64  scopeid 0x20<link>
        ether 00:04:4b:c5:38:c0  txqueuelen 1000  (Ethernet)
        RX packets 5260737  bytes 2314536032 (2.3 GB)
        RX errors 0  dropped 343548  overruns 0  frame 0
        TX packets 439593  bytes 3740304935 (3.7 GB)
        TX errors 1006  dropped 0 overruns 0  carrier 1006  collisions 0
        device interrupt 41

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 198701  bytes 16740804 (16.7 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 198701  bytes 16740804 (16.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:04:4b:c5:38:be  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

From the errors I see it looks as if there is no possibility of a successful test (or most any kind of ethernet on the particular interface).

Prior to test shows eth0 has an enormous amount of dropped RX traffic, and an enormous amount of TX errors (1 or 2 “error” would be unacceptable, 1006 is probably worth considering 100% failure). So before the test ever started the network was failed. Something is quite wrong before the test ever started. Is this the cat 6 cross over cable case?

The carrier error is itself possibly from electrical failure (a bad cable or perhaps bent pin), or from configuration error, e.g., one side thinks it is full duplex, while the other side thinks it is half duplex.

What do you see on the Jetson and the host via the command “route”?

I am going to pretend both Jetson and host use the name “eth0” for that connection, but adjust as needed. What is the output on both (before test) for:

sudo ethtool eth0

(make sure the cables are correctly connected prior to booting the Jetson…I’m hoping to eliminate showing errors for any time the cable is not plugged in)

nvidia@tegra-tx2:~$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
nvidia@tegra-tx2:~$ sudo ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 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/Half 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: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

The host is a windows PC.

I do not see any errors in either the route or the software’s reporting on the PHY. Auto negotiation is on, and MTU is a default/standard 1500, and so I do not see anything wrong from the Linux side.

You could try to do the same test with another Linux computer instead of Windows, but I lack any ability to debug what is going wrong on the Windows side. If you have a high end managed switch in between (but from what you said probably not), then switch settings could cause issues. The best I can do is suggest something is wrong either in the cabling or in the Windows configuration. Testing against a Linux host and seeing if there are still issues with errors/overruns/framing, so on, would tell you that cabling is in the way; or conversely, that if no issues occur there, it is a Windows configuration issue.

I have installed ubuntu16.04 on the PC with Intel I210 NIC.
The PC with ubuntu can finish the test ,although the NIC has auto reset(link down and link up) severl times by itself.
Here is the cmd output
Before test
The Jetson

nvidia@tegra-tx2:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.79  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::204:4bff:fec5:38c0  prefixlen 64  scopeid 0x20<link>
        ether 00:04:4b:c5:38:c0  txqueuelen 1000  (Ethernet)
        RX packets 453288189  bytes 625542007384 (625.5 GB)
        RX errors 0  dropped 489389  overruns 0  frame 0
        TX packets 102128283  bytes 423575933622 (423.5 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 41  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 40172803  bytes 1252581996656 (1.2 TB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 40172803  bytes 1252581996656 (1.2 TB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:04:4b:c5:38:be  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

The PC

kxxxx@kxxxx-a:~$ ifconfig enp3s0
enp3s0    Link encap:Ethernet  HWaddr 80:7b:85:50:12:61  
          inet addr:192.168.1.67  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::827b:85ff:fe50:1261/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6304032 errors:0 dropped:0 overruns:3 frame:0
          TX packets:5407398 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8733655154 (8.7 GB)  TX bytes:7472257412 (7.4 GB)
          Memory:df200000-df27ffff
kxxxx@kxxxx-a:~$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 enp3s0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 enp3s0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 enp3s0

After test
The Jetson TX2

nvidia@tegra-tx2:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.79  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::204:4bff:fec5:38c0  prefixlen 64  scopeid 0x20<link>
        ether 00:04:4b:c5:38:c0  txqueuelen 1000  (Ethernet)
        RX packets 533679780  bytes 737085329072 (737.0 GB)
        RX errors 0  dropped 489389  overruns 0  frame 0
        TX packets 113363948  bytes 531685319031 (531.6 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 41  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 40177375  bytes 1252582347357 (1.2 TB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 40177375  bytes 1252582347357 (1.2 TB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c6:17:de:67:c1:8f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:04:4b:c5:38:be  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

The PC

kxxxxx@kxxxxx-a:~$ ifconfig enp3s0
enp3s0    Link encap:Ethernet  HWaddr 80:7b:85:50:12:61  
          inet addr:192.168.1.67  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::827b:85ff:fe50:1261/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:83655958 errors:0 dropped:0 overruns:8 frame:0
          TX packets:80392689 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:112889113253 (112.8 GB)  TX bytes:112668277180 (112.6 GB)
          Memory:df200000-df27ffff

The Jeston dmesg

nvidia@tegra-tx2:~$ dmesg --follow
[三 12月 18 19:00:53 2019] tegra_wdt_t18x 30c0000.watchdog: Watchdog(0): wdt timeout set to 1200 sec
[三 12月 18 19:00:53 2019] watchdog: watchdog0: watchdog did not stop!
[三 12月 18 19:03:26 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:03:29 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:05:54 2019] tegra_wdt_t18x 30c0000.watchdog: Watchdog(0): wdt timeout set to 1200 sec
[三 12月 18 19:05:54 2019] watchdog: watchdog0: watchdog did not stop!
[三 12月 18 19:08:04 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:08:07 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:08:28 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:08:45 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:08:51 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:09:01 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:09:08 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:09:11 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:09:33 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:09:42 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:09:45 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:09:51 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:09:58 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:10:04 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:10:06 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:10:06 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:10:17 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:10:20 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:10:36 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:11:01 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:11:04 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:11:10 2019] tegra_wdt_t18x 30c0000.watchdog: Watchdog(0): wdt timeout set to 1200 sec
[三 12月 18 19:11:10 2019] watchdog: watchdog0: watchdog did not stop!
[三 12月 18 19:11:12 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:11:20 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:11:23 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:11:28 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:11:38 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:11:46 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:11:47 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:12:05 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:12:05 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:12:11 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:12:19 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:12:23 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:12:26 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:12:34 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:12:37 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:12:59 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:13:19 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:13:22 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:13:43 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:13:46 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:14:19 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:14:26 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:14:26 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:14:33 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:14:36 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:14:46 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:14:56 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:15:02 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:15:05 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:15:14 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:15:37 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:15:40 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:15:53 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:16:06 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:16:09 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:16:11 2019] tegra_wdt_t18x 30c0000.watchdog: Watchdog(0): wdt timeout set to 1200 sec
[三 12月 18 19:16:11 2019] watchdog: watchdog0: watchdog did not stop!
[三 12月 18 19:16:22 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:16:23 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:16:36 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:16:39 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:16:51 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:16:51 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:16:56 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:17:02 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:17:04 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:17:05 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:17:30 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:17:33 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:17:46 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:18:05 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:18:08 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:18:35 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:18:39 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:18:54 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:18:57 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:19:04 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:19:28 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:19:31 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:19:42 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:19:48 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:19:51 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:19:58 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:20:12 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:20:15 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:20:37 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:20:57 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:21:00 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:21:12 2019] tegra_wdt_t18x 30c0000.watchdog: Watchdog(0): wdt timeout set to 1200 sec
[三 12月 18 19:21:12 2019] watchdog: watchdog0: watchdog did not stop!
[三 12月 18 19:21:18 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:21:28 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:21:31 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:21:32 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:21:33 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:21:39 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:21:42 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:21:56 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:21:59 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:22:14 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:22:16 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:22:18 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:22:25 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:22:28 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:22:40 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:23:05 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:23:08 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:23:18 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:23:34 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:23:37 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:24:15 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:24:15 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:24:39 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:24:46 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:24:49 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[三 12月 18 19:24:53 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:25:14 2019] eqos 2490000.ether_qos eth0: eqos_start_xmit(): TX ring full for queue 0
[三 12月 18 19:25:20 2019] eqos 2490000.ether_qos eth0: Link is Down
[三 12月 18 19:25:23 2019] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx

The PC dmesg

[三 12月 18 19:03:26 2019] ------------[ cut here ]------------
[三 12月 18 19:03:26 2019] NETDEV WATCHDOG: enp3s0 (igb): transmit queue 0 timed out
[三 12月 18 19:03:26 2019] WARNING: CPU: 2 PID: 0 at /build/linux-hwe-ngR1Rd/linux-hwe-4.15.0/net/sched/sch_generic.c:323 dev_watchdog+0x222/0x230
[三 12月 18 19:03:26 2019] Modules linked in: joydev input_leds hid_generic usbhid hid nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal snd_soc_skl intel_powerclamp snd_soc_skl_ipc coretemp snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi kvm_intel kvm snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hda_core snd_hwdep ghash_clmulni_intel pcbc snd_pcm aesni_intel snd_seq_midi snd_seq_midi_event aes_x86_64 crypto_simd snd_rawmidi glue_helper cryptd intel_cstate intel_rapl_perf snd_seq snd_seq_device snd_timer snd soundcore shpchp mei_me mei intel_pch_thermal acpi_pad mac_hid parport_pc ppdev lp parport autofs4 i915 e1000e drm_kms_helper syscopyarea sysfillrect sysimgblt
[三 12月 18 19:03:26 2019]  fb_sys_fops uas igb dca i2c_algo_bit ahci ptp pps_core drm usb_storage libahci video pinctrl_sunrisepoint
[三 12月 18 19:03:26 2019] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.15.0-72-generic #81~16.04.1-Ubuntu
[三 12月 18 19:03:26 2019] Hardware name: Default string AIMG/V2C, BIOS 1.10 06/18/2019
[三 12月 18 19:03:26 2019] RIP: 0010:dev_watchdog+0x222/0x230
[三 12月 18 19:03:26 2019] RSP: 0018:ffff9e7dedd03e68 EFLAGS: 00010282
[三 12月 18 19:03:26 2019] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000083f
[三 12月 18 19:03:26 2019] RDX: 0000000000000000 RSI: 00000000000000f6 RDI: 000000000000083f
[三 12月 18 19:03:26 2019] RBP: ffff9e7dedd03e98 R08: 0000000000000001 R09: 000000000000037d
[三 12月 18 19:03:26 2019] R10: 0000000000000000 R11: 000000000000037d R12: 0000000000000008
[三 12月 18 19:03:26 2019] R13: ffff9e7dd9fa4000 R14: ffff9e7dd9fa4478 R15: ffff9e7dda052940
[三 12月 18 19:03:26 2019] FS:  0000000000000000(0000) GS:ffff9e7dedd00000(0000) knlGS:0000000000000000
[三 12月 18 19:03:26 2019] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[三 12月 18 19:03:26 2019] CR2: 00007f35802b1018 CR3: 000000013360a003 CR4: 00000000003606e0
[三 12月 18 19:03:26 2019] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[三 12月 18 19:03:26 2019] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[三 12月 18 19:03:26 2019] Call Trace:
[三 12月 18 19:03:26 2019]  <IRQ>
[三 12月 18 19:03:26 2019]  ? dev_deactivate_queue.constprop.33+0x60/0x60
[三 12月 18 19:03:26 2019]  call_timer_fn+0x32/0x140
[三 12月 18 19:03:26 2019]  run_timer_softirq+0x1e9/0x430
[三 12月 18 19:03:26 2019]  ? ktime_get+0x3e/0xb0
[三 12月 18 19:03:26 2019]  ? lapic_next_deadline+0x26/0x30
[三 12月 18 19:03:26 2019]  __do_softirq+0xf5/0x2a8
[三 12月 18 19:03:26 2019]  irq_exit+0xca/0xd0
[三 12月 18 19:03:26 2019]  smp_apic_timer_interrupt+0x79/0x150
[三 12月 18 19:03:26 2019]  apic_timer_interrupt+0x8c/0xa0
[三 12月 18 19:03:26 2019]  </IRQ>
[三 12月 18 19:03:26 2019] RIP: 0010:cpuidle_enter_state+0xa7/0x300
[三 12月 18 19:03:26 2019] RSP: 0018:ffffb17dc0d03e60 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff11
[三 12月 18 19:03:26 2019] RAX: ffff9e7dedd21840 RBX: 0000000000000006 RCX: 000000000000001f
[三 12月 18 19:03:26 2019] RDX: 0000000000000000 RSI: 00000000378e38e3 RDI: 0000000000000000
[三 12月 18 19:03:26 2019] RBP: ffffb17dc0d03e98 R08: fffffffb26d74a95 R09: 0000000000000018
[三 12月 18 19:03:26 2019] R10: ffffb17dc0d03e30 R11: 0000000000003429 R12: 0000000000000006
[三 12月 18 19:03:26 2019] R13: ffff9e7dedd2b900 R14: ffffffffbb973498 R15: 000000a49e694ed4
[三 12月 18 19:03:26 2019]  cpuidle_enter+0x17/0x20
[三 12月 18 19:03:26 2019]  call_cpuidle+0x23/0x40
[三 12月 18 19:03:26 2019]  do_idle+0x197/0x200
[三 12月 18 19:03:26 2019]  cpu_startup_entry+0x73/0x80
[三 12月 18 19:03:26 2019]  start_secondary+0x1ab/0x200
[三 12月 18 19:03:26 2019]  secondary_startup_64+0xa5/0xb0
[三 12月 18 19:03:26 2019] Code: 36 00 49 63 4e e8 eb 92 4c 89 ef c6 05 69 fa d6 00 01 e8 12 19 fd ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 d0 e8 58 bb e8 2e e6 7e ff <0f> 0b eb c0 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 
[三 12月 18 19:03:26 2019] ---[ end trace 16ded2ffbe14c72d ]---
[三 12月 18 19:03:26 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:03:29 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:08:03 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:08:03 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:08:05 2019] igb 0000:03:00.0: exceed max 2 second
[三 12月 18 19:08:05 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Down
[三 12月 18 19:08:07 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:09:07 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:09:07 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:09:09 2019] igb 0000:03:00.0: exceed max 2 second
[三 12月 18 19:09:09 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Down
[三 12月 18 19:09:11 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:09:41 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:09:45 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:10:16 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:10:20 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:11:00 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:11:04 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:11:19 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:11:23 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:12:19 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:12:23 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:12:33 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:12:37 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:13:18 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:13:22 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:13:42 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:13:46 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:14:32 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:14:36 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:15:01 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:15:05 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:15:36 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:16:05 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:16:09 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:16:35 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:16:35 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:16:37 2019] igb 0000:03:00.0: exceed max 2 second
[三 12月 18 19:16:37 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Down
[三 12月 18 19:16:39 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:17:29 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:17:29 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:17:31 2019] igb 0000:03:00.0: exceed max 2 second
[三 12月 18 19:17:31 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Down
[三 12月 18 19:17:33 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:18:04 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:18:08 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:18:53 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:18:53 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:18:55 2019] igb 0000:03:00.0: exceed max 2 second
[三 12月 18 19:18:55 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Down
[三 12月 18 19:18:57 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:19:27 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:19:31 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:19:47 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:19:47 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:19:49 2019] igb 0000:03:00.0: exceed max 2 second
[三 12月 18 19:19:49 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Down
[三 12月 18 19:19:51 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:20:11 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:20:15 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:20:56 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:21:00 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:21:55 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:21:59 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:22:24 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:22:28 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:23:04 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:23:08 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:23:33 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:23:37 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:24:46 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:24:49 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[三 12月 18 19:25:19 2019] igb 0000:03:00.0 enp3s0: Reset adapter
[三 12月 18 19:25:23 2019] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
kxxxxx@kxxxxx-a:~$ ethtool enp3s0
Settings for enp3s0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Speed: 1000Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes

Before test, Jetson side, has a lot of dropped RX packets. PC side has a few overruns.

After test, the Jetson side RX dropped packets is the same count: 489389.

After test, the PC side has increased overruns.

The dmesg of the Jetson makes me believe that either the application on the Jetson working with the data is failing, or else the physical networking is failing (e.g., signal quality).

The dmesg of the PC after the test shows some serious problems, perhaps with the IGB driver, but those dmesg reactions could just be the visible reaction to some other network hardware issue.

I am inclined to believe it is likely that there is some signal issue between directly connected units with the cross-over cable, but since the issue goes away through the switch, it seems you will need a method to evaluate signal quality. Probably the only simple and easy test at this point is to try a new cable from some different design (e.g., if this was ordered from someone, find a different brand to try, or build your own if this was not already custom built…if it was already custom built, then likely something went wrong).

Beyond this you may end up looking at eye patterns or other ethernet quality testing.

One more thing to test: If the same Intel gigabit adapter was used on both the Windows system and the Linux PC, then perhaps that adapter has issues.

Every time two devices connect on a differential pair you will get different inductance/capacitance/impedance, and two otherwise technically working devices may combine to provide a signal which is out of range of the devices. That intermediate device (the switch) might simply have better tolerance to signal issues, or due to different inductance/capacitance/impedance, may not need a better tolerance to signal quality. However, keep in mind that even before the test both sides were experiencing various errors…it wasn’t just at the Jetson side. This partial function in direct connect, combined with lack of failure through a switch is fairly strong evidence of a signal quality issue, but I can’t guarantee it. A link constantly dropping out and coming back is just the link’s way of trying to reset in hopes that any failure is only temporary. Because there are errors before the test ever begins, this once more tends to indicate physical network failures, and not failures with the applications.

Both NICs seem to report they are able to auto negotiate, and so I do not believe it is a case of incompatible settings.