Hello,
Does anybody has experience on l4tbr0 problem would shed a light what might be the root cause or how to resolve it ?
After flashing Jetpack 4.3 on Jetson Nano Prod Module and let it boot up, sometimes l4tbr0 is missing, sometimes l4tbr0 shows up but it has only Tx packets without any Rx packets. Host machine sometimes can see Nvidia from lsusb, sometimes not but in anyway host machine cannot ping Jetson Nano.
This happened on multiple boards at different areas. One board does not work in my office, it works fine in other office.
When l4tbr0 shows up but not fully work, the nv-l4t-usb-device-mode.service is loaded successfully and active (exited), status=0/SUCCESS. Restart this service does not resolve the issue.
On host machine, lsusb can find Nvidia device.
on host machine:
$ ping -c 2 192.168.55.1
PING 192.168.55.1 (192.168.55.1) 56(84) bytes of data.
— 192.168.55.1 ping statistics —
2 packets transmitted, 0 received, 100% packet loss, time 1000ms
on Jetson Nano
guest@localhost:~$ ifconfig l4tbr0
l4tbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.55.1 netmask 255.255.255.0 broadcast 192.168.55.255
inet6 fe80::1 prefixlen 128 scopeid 0x20
inet6 fe80::428:5eff:fe03:65e5 prefixlen 64 scopeid 0x20
ether 06:28:5e:03:65:e5 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 291 bytes 14200 (14.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
guest@localhost:~$ sudo ethtool -i l4tbr0
driver: bridge
version: 2.3
firmware-version: N/A
expansion-rom-version:
bus-info: N/A
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
guest@localhost:~$ sudo systemctl restart nv-l4t-usb-device-mode.service
[ 587.932216] using random self ethernet address
[ 587.932218] using random host ethernet address
[ 588.232692] using random self ethernet address
[ 588.237192] using random host ethernet address
guest@localhost:~$ sudo systemctl status nv-l4t-usb-device-mode.service
nv-l4t-usb-device-mode.service - Configure USB flashing port for device mode
Loaded: loaded (/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode.servic
Active: active (exited) since Mon 2018-01-29 00:09:14 CST; 7s ago
Process: 1811 ExecStopPost=/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-m
Process: 2334 ExecStart=/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode
Main PID: 2334 (code=exited, status=0/SUCCESS)
Jan 29 00:09:13 localhost.localdomain systemd[1]: Starting Configure USB flashin
Jan 29 00:09:14 localhost.localdomain nv-l4t-usb-device-mode-start.sh[2334]: /
Jan 29 00:09:14 localhost.localdomain systemd[1]: Started Configure USB flashing
Regards
- Steven