[dpdk-users] qdisc errors on 20.11.1 & Azure

[Tyler Blair]

> The next thing to check is version of rdma-core. Long just diagnosed an issue with rdma-core version in Ubuntu 20.4

That's the version I'm using in my last reply -- from ppa:canonical-server/server-backports: 33.1-1ubuntu1~backport20.04-202103240925~ubuntu20.04.1

Noticed now, but with the new kernal and rdma-core librdmacm-dev from backports there are some new mlx5_pci errors. Appears to be working OK otherwise though.

EAL: Detected 8 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: Probe PCI driver: mlx5_pci (15b3:1016) device: 5ed7:00:02.0 (socket 0)
** mlx5_pci: Failed to allocate Tx DevX UAR (BF)
** mlx5_pci: Failed to allocate Rx DevX UAR (BF)
** mlx5_pci: No available register for Sampler.
** mlx5_pci: Size 0xFFFF is not power of 2, will be aligned to 0x10000.
net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3)
tap_nl_dump_ext_ack(): Cannot delete qdisc with handle of zero
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
Warning: NUMA should be configured manually by using --port-numa-config and --ring-numa-config parameters along with --numa.
testpmd: create a new mbuf pool <mb_pool_0>: n=155456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Warning! port-topology=paired and odd forward ports number, the last port will pair with itself.
Configuring Port 1 (socket 0)
Port 1: 00:22:48:3B:AB:CC
Checking link statuses...

Marked with ** - these appear to be pretty benign as well though.

Regards,
Tyler