Dear Aaeon,
On BOXER-8250AI Jetpack 5.0.x or Jetson Linux 34.X/35.X under kernel 5.10.104-tegra using igb driver the ping can go from 50-1000ms. However, on Jetpack 4.6.2 Jetson Linux 32.7/32.6 Linux kernel 4.9.253-tegra, we can get reliable ~0.5 ms ping.
The problem is similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939200
I know Jetpack 5.0.x is not supported. But I report this issue to get some feedback on the future direction. Do we patch the kernel or there will be a hardware revision in the future (according to our testing Jetpack 5.0.x work fine in BOXER-8253AI-A1-1011 using igb version: 5.10.104-tegra)?
On Jetpack 5.0.x
$ sudo ethtool -i eth0
driver: igb
version: 5.10.104-tegra
firmware-version: 3.11, 0x8000046e
expansion-rom-version:
bus-info: 0005:03:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
$ ping 192.168.55.1
PING 192.168.55.1 (192.168.55.1) 56(84) bytes of data.
64 bytes from 192.168.55.1: icmp_seq=1 ttl=64 time=55.1 ms
64 bytes from 192.168.55.1: icmp_seq=2 ttl=64 time=382 ms
64 bytes from 192.168.55.1: icmp_seq=3 ttl=64 time=288 ms
64 bytes from 192.168.55.1: icmp_seq=4 ttl=64 time=1041 ms
64 bytes from 192.168.55.1: icmp_seq=5 ttl=64 time=58.9 ms
64 bytes from 192.168.55.1: icmp_seq=6 ttl=64 time=547 ms
64 bytes from 192.168.55.1: icmp_seq=7 ttl=64 time=270 ms
64 bytes from 192.168.55.1: icmp_seq=8 ttl=64 time=1054 ms
64 bytes from 192.168.55.1: icmp_seq=9 ttl=64 time=59.0 ms
64 bytes from 192.168.55.1: icmp_seq=10 ttl=64 time=1043 ms
64 bytes from 192.168.55.1: icmp_seq=11 ttl=64 time=61.3 ms
^C
--- 192.168.55.1 ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10067ms
On Jetpack 4.6.2
$ sudo ethtool -i eth1
driver: igb
version: 5.4.0-k
firmware-version: 3.11, 0x8000046e
expansion-rom-version:
bus-info: 0005:03:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
$ ping 192.168.55.1
PING 192.168.55.1 (192.168.55.1) 56(84) bytes of data.
64 bytes from 192.168.55.1: icmp_seq=1 ttl=64 time=0.563 ms
64 bytes from 192.168.55.1: icmp_seq=2 ttl=64 time=0.504 ms
64 bytes from 192.168.55.1: icmp_seq=3 ttl=64 time=0.492 ms
64 bytes from 192.168.55.1: icmp_seq=4 ttl=64 time=0.498 ms
64 bytes from 192.168.55.1: icmp_seq=5 ttl=64 time=0.493 ms
64 bytes from 192.168.55.1: icmp_seq=6 ttl=64 time=0.503 ms
64 bytes from 192.168.55.1: icmp_seq=7 ttl=64 time=0.473 ms
64 bytes from 192.168.55.1: icmp_seq=8 ttl=64 time=0.500 ms
64 bytes from 192.168.55.1: icmp_seq=9 ttl=64 time=0.581 ms
64 bytes from 192.168.55.1: icmp_seq=10 ttl=64 time=0.337 ms
64 bytes from 192.168.55.1: icmp_seq=11 ttl=64 time=0.534 ms
64 bytes from 192.168.55.1: icmp_seq=12 ttl=64 time=0.484 ms
64 bytes from 192.168.55.1: icmp_seq=13 ttl=64 time=0.493 ms
^C
--- 192.168.55.1 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12275ms
rtt min/avg/max/mdev = 0.337/0.496/0.581/0.059 ms
Hi Sir,
AAEON has not yet produced images for jetpack 5.0. Therefore, we are unable to respond to this question at this time.
But thank you very much for providing us with this information!
We will pay special attention to this issue in the future.
Best Regards,
Neptune Liu