

DPAA Ethernet functionality has become worse..
For example these weird ping responses to the same addresses... and after 12 packets it stops
It has to be the QMAN/BMAN buffer DPAA part of the driver. Its only when using the DPAA ethernet adapter. Every other NIC is working.
The Freescale DPAA architecture consists of a series of hardware blocks
that support Ethernet connectivity. The Ethernet driver depends upon the
following drivers in the Linux kernel:
- Peripheral Access Memory Unit (PAMU) (* needed only for PPC platforms)
drivers/iommu/fsl_*
- Frame Manager (FMan)
drivers/net/ethernet/freescale/fman
- Queue Manager (QMan), Buffer Manager (BMan)
drivers/soc/fsl/qbman
https://www.kernel.org/doc/Documentatio ... g/dpaa.txt
root@X5000LNX:/home/skateman# sh ethernetup.sh
resetting the transceiver...
root@X5000LNX:/home/skateman# ping www.nu.nl
PING nunl.aws.sanomaservices.nl (54.192.2.63) 56(84) bytes of data.
64 bytes from 54.192.2.63: icmp_seq=1 ttl=242 time=24.0 ms
64 bytes from 54.192.2.63: icmp_seq=2 ttl=242 time=20.9 ms
64 bytes from 54.192.2.63: icmp_seq=3 ttl=242 time=19.5 ms
64 bytes from 54.192.2.63: icmp_seq=4 ttl=242 time=22.6 ms
64 bytes from 54.192.2.63: icmp_seq=5 ttl=242 time=19.6 ms
64 bytes from 54.192.2.63: icmp_seq=6 ttl=242 time=20.7 ms
64 bytes from 54.192.2.63: icmp_seq=7 ttl=242 time=19.1 ms
64 bytes from 54.192.2.63: icmp_seq=8 ttl=242 time=21.3 ms
64 bytes from 54.192.2.63: icmp_seq=9 ttl=242 time=22.1 ms
64 bytes from 54.192.2.63: icmp_seq=10 ttl=242 time=19.1 ms
64 bytes from 54.192.2.63: icmp_seq=11 ttl=242 time=19.5 ms
64 bytes from 54.192.2.63: icmp_seq=12 ttl=242 time=20.5 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
^C
--- nunl.aws.sanomaservices.nl ping statistics ---
17 packets transmitted, 12 received, 29% packet loss, time 44178ms
rtt min/avg/max/mdev = 19.105/20.792/24.046/1.489 ms
root@X5000LNX:/home/skateman# ping www.nu.nl
PING nunl.aws.sanomaservices.nl (54.192.2.109) 56(84) bytes of data.
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=1 ttl=240 time=19.8 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=2 ttl=240 time=18.5 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=3 ttl=240 time=19.4 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=4 ttl=240 time=18.6 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=5 ttl=240 time=19.5 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=6 ttl=240 time=19.3 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=7 ttl=240 time=17.6 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=8 ttl=240 time=24.7 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=9 ttl=240 time=19.5 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=10 ttl=240 time=18.4 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=11 ttl=240 time=49.8 ms
64 bytes from server-54-192-2-109.lhr5.r.cloudfront.net (54.192.2.109): icmp_seq=12 ttl=240 time=18.3 ms
^C
--- nunl.aws.sanomaservices.nl ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 23526ms
rtt min/avg/max/mdev = 17.664/22.001/49.804/8.560 ms