AnsweredAssumed Answered

imx6 android5.1 ping丢包

Question asked by zhiqiang wang on Jul 24, 2018
Latest reply on Aug 7, 2018 by zhiqiang wang

我的硬件平台以太网phy芯片用的是ar8033,最开始使用android4.4.2时以太网工作正常。

后来软件更新到android5.1版本,以太网ping就会出现丢包,如下情况:

root@sabresd_6dq:/ # ping 192.168.9.127
PING 192.168.9.127 (192.168.9.127) 56(84) bytes of data.
64 bytes from 192.168.9.127: icmp_seq=1 ttl=64 time=998 ms
64 bytes from 192.168.9.127: icmp_seq=2 ttl=64 time=0.544 ms
64 bytes from 192.168.9.127: icmp_seq=3 ttl=64 time=0.288 ms
64 bytes from 192.168.9.127: icmp_seq=5 ttl=64 time=0.257 ms
64 bytes from 192.168.9.127: icmp_seq=6 ttl=64 time=0.379 ms
64 bytes from 192.168.9.127: icmp_seq=7 ttl=64 time=0.435 ms
64 bytes from 192.168.9.127: icmp_seq=8 ttl=64 time=0.397 ms
64 bytes from 192.168.9.127: icmp_seq=9 ttl=64 time=0.271 ms
64 bytes from 192.168.9.127: icmp_seq=10 ttl=64 time=0.358 ms
64 bytes from 192.168.9.127: icmp_seq=11 ttl=64 time=0.360 ms
64 bytes from 192.168.9.127: icmp_seq=12 ttl=64 time=0.361 ms
64 bytes from 192.168.9.127: icmp_seq=13 ttl=64 time=0.470 ms
64 bytes from 192.168.9.127: icmp_seq=14 ttl=64 time=0.445 ms
64 bytes from 192.168.9.127: icmp_seq=15 ttl=64 time=0.259 ms
64 bytes from 192.168.9.127: icmp_seq=16 ttl=64 time=0.396 ms
64 bytes from 192.168.9.127: icmp_seq=17 ttl=64 time=0.376 ms
64 bytes from 192.168.9.127: icmp_seq=18 ttl=64 time=0.330 ms
64 bytes from 192.168.9.127: icmp_seq=19 ttl=64 time=0.334 ms
64 bytes from 192.168.9.127: icmp_seq=20 ttl=64 time=0.353 ms
64 bytes from 192.168.9.127: icmp_seq=21 ttl=64 time=0.356 ms
64 bytes from 192.168.9.127: icmp_seq=22 ttl=64 time=0.351 ms
64 bytes from 192.168.9.127: icmp_seq=23 ttl=64 time=0.436 ms
64 bytes from 192.168.9.127: icmp_seq=24 ttl=64 time=0.261 ms
64 bytes from 192.168.9.127: icmp_seq=26 ttl=64 time=0.343 ms
64 bytes from 192.168.9.127: icmp_seq=27 ttl=64 time=0.342 ms
^C
--- 192.168.9.127 ping statistics ---
27 packets transmitted, 25 received, 7% packet loss, time 25997ms
rtt min/avg/max/mdev = 0.257/40.297/998.724/195.638 ms

Outcomes