Problem with Networking Driver

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX1
1

Hi,
Jetson TX1 lost internet connetion. After checking the kernal log, I found maybe something wrong with Networking Driver. Is there any records about Networking Driver problem? This is a part of kernal log.

Thanks!

Dec 31 10:27:28 tegra-ubuntu kernel: [214259.916225] r8152 2-1:1.0 eth0: carrier off
Dec 31 10:27:30 tegra-ubuntu kernel: [214262.086721] r8152 2-1:1.0 eth0: carrier on
Dec 31 13:41:32 tegra-ubuntu kernel: [225904.073894] r8152 2-1:1.0 eth0: carrier off
Dec 31 13:41:34 tegra-ubuntu kernel: [225906.054133] r8152 2-1:1.0 eth0: carrier on
Jan  3 12:09:48 tegra-ubuntu kernel: [479603.293972] r8152 2-1:1.0 eth0: carrier off
Jan  3 12:10:02 tegra-ubuntu kernel: [479618.038797] r8152 2-1:1.0 eth0: carrier on
Jan  3 12:10:27 tegra-ubuntu kernel: [479642.909705] r8152 2-1:1.0 eth0: carrier off
Jan  3 12:10:29 tegra-ubuntu kernel: [479645.175363] r8152 2-1:1.0 eth0: carrier on
Jan  3 12:10:30 tegra-ubuntu kernel: [479645.565694] r8152 2-1:1.0 eth0: carrier off
Jan  3 12:10:32 tegra-ubuntu kernel: [479648.087082] r8152 2-1:1.0 eth0: carrier on
Jan  3 12:11:11 tegra-ubuntu kernel: [479687.004568] r8152 2-1:1.0 eth0: carrier off
Jan  3 12:11:13 tegra-ubuntu kernel: [479689.143348] r8152 2-1:1.0 eth0: carrier on
Jan  3 12:11:16 tegra-ubuntu kernel: [479692.155682] r8152 2-1:1.0 eth0: carrier off
Jan  3 12:11:18 tegra-ubuntu kernel: [479694.070176] r8152 2-1:1.0 eth0: carrier on
Jan  3 12:11:19 tegra-ubuntu kernel: [479695.227771] r8152 2-1:1.0 eth0: carrier off
Jan  3 12:11:22 tegra-ubuntu kernel: [479697.269449] r8152 2-1:1.0 eth0: carrier on
Jan  3 12:11:31 tegra-ubuntu kernel: [479707.131786] r8152 2-1:1.0 eth0: carrier off
Jan  3 12:11:33 tegra-ubuntu kernel: [479709.077523] r8152 2-1:1.0 eth0: carrier on
2

Jasonychen,

Please share more detail about this issue.

  1. BSP revision
  2. Custom board/ devkit
  3. Reproducible or not
  4. How to reproduce
3

Hi,

BSP version: R28.2.1 (kernel-4.4).
AND it’s a Custom board provided by LeeTop which is your partner.
We found three cases on our online devices. But we haven’t tried to reproduce on our test environment at present.

4

Hi,
Network can recover by restart devices(turn off the power and plug in the power).

5

Not sure this is to specific device or software bug, looks like it keeps auto-resume.

Could you try to use that module on devkit and try to reproduce? Even if it is from our partner, we still suggest to use nv devkit to reproduce issue.

Please make sure it is an issue that can keep reproducing.

6

Alright, we’ll try our best to reproduce.
Did you have the same problem in your knowledge base?

7

I didn’t see such error case before. As you know, if this is a common case, many users may have reported.

8

Hello WayneWWW,

More and more on site working devices occurs this phenomenon. We receied many complaints from our customer.

Can you help analyse this phenomenon and try to reproduce?

9

Jasonychen,

Are all issues happened on custom carrier board or devkit? How long do you hit this issue after boot up?

10

All issues happened on custom carrier board. I can’t give a certain period because this phenomenon occurs in the several hours after boot up or several days or several weeks on different custom carrier board.

11

Dear Jasonychen,

Please help to check these devices are in some location or different location, and their log are the same like “carrier on, carrier off”?

Can you provide the whole kernel logs ? Thanks.

1.netif_carrier_on

【作用】告知内核子系统网络链接完整。

  1. netif_carrier_off

【作用】告知内核子系统网络断开。

12

Dear WayneWWW,

It seems the network connection is broken and re-connected from the log, and we have not seen this before on this carrier board, and it happened just in this period of time.
I attached the log files in /var/log folder, sent by the end user.
1190log.zip (727 KB)
1175log.zip (866 KB)

13

Hi LeeTop,

May I double confirm that end user hits the same error? Your log only has one line “r8152 2-1:1.0 eth0: carrier off”.

Also, could you check the usecase/environment of this issue? We would like to test it on our devkit.

14

Hello,

we are using Orbitty-Boards together with TX1 Modules and are having the same issue.
The link and the interface (eth0) go down und up again which currently makes the boards unusable in production.
The cause of the USB-Resets on usb 2-2 is also unclear. We have some usb3 streaming device on 2-2…

[709946.682906] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[709951.382911] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[710192.826664] r8152 2-1:1.0 eth0: carrier off
[710196.403137] r8152 2-1:1.0 eth0: carrier on
[710197.852368] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[710198.277731] usb 2-2: reset SuperSpeed USB device number 3 using xhci-tegra
[710199.323746] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710199.546349] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710199.569051] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710203.130564] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[710206.349888] usb 2-2: reset SuperSpeed USB device number 3 using xhci-tegra
[710207.395931] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710207.625157] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710207.644386] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710215.224290] r8152 2-1:1.0 eth0: carrier off
[710218.899884] r8152 2-1:1.0 eth0: carrier on
[710224.588945] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[710226.378327] usb 2-2: reset SuperSpeed USB device number 3 using xhci-tegra
[710227.422820] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710227.644532] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710227.663596] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710227.983833] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[710302.199902] r8152 2-1:1.0 eth0: carrier off
[710306.036460] r8152 2-1:1.0 eth0: carrier on
[710307.954794] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[710308.412095] usb 2-2: reset SuperSpeed USB device number 3 using xhci-tegra
[710309.458969] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710309.499145] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[710309.685637] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710309.705547] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[710507.594800] tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000
[711570.761692] r8152 2-1:1.0 eth0: carrier off
[711574.402485] r8152 2-1:1.0 eth0: carrier on
[715995.916882] usb 2-2: reset SuperSpeed USB device number 3 using xhci-tegra
[715996.960027] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[715997.182024] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[715997.200772] xhci-tegra 70090000.xusb: WARN Event TRB for slot 2 ep 2 with no TDs queued?
15

maaax,

Please file a new topic for this issue. leetop has clarified their issue as hardware design problem.
It seems not directly related to yours.