dpdk-pdump error:

Trying to use dpdp-pdump to capture packet:

dpdk-pdump – --pdump ‘port=0,queue=*,rx-dev=/tmp/a’

EAL: Detected 12 lcore(s)

EAL: Probing VFIO support…

EAL: PCI device 0000:08:00.0 on NUMA socket 0

EAL: probe driver: 15b3:1015 net_mlx5

PMD: mlx5.c:419: mlx5_pci_probe(): PCI information matches, using device “mlx5_0” (SR-IOV: false, MPS: true)

PMD: mlx5.c:442: mlx5_pci_probe(): 1 port(s) detected

PMD: mlx5.c:590: mlx5_pci_probe(): port 1 MAC address is 24:8a:07:8b:25:30

PMD: mlx5.c:638: mlx5_pci_probe(): no private data for port 0

EAL: Error - exiting with code: 1

Cause: Requested device 0000:08:00.0 cannot be used

0000:08:00.0 is one of the Mellanox 10G [the first 2 is 10G Dual-port]:

Network devices using kernel driver

===================================

0000:08:00.0 ‘MT27710 Family [ConnectX-4 Lx]’ if=enp8s0f0 drv=mlx5_core unused=igb_uio

0000:08:00.1 ‘MT27710 Family [ConnectX-4 Lx]’ if=enp8s0f1 drv=mlx5_core unused=igb_uio

0000:0a:00.0 ‘MT27710 Family [ConnectX-4 Lx]’ if=enp10s0 drv=mlx5_core unused=igb_uio

testpmd would also cause segmentation fault

Hello

I am encountering similar issue on Mellanox NIC (driver version version: 3.4-2.0.0 (23 Nov 2016); firmware-version: 2.36.5000) when launching DPDK app in secondary process mode:

PMD: net_mlx4: no private data for port 0

I tried to get more info by enabling debug flag:

CONFIG_RTE_LIBRTE_MLX4_DEBUG=y

But after enabling debug flag even primary process is crashing:

testpmd: /root/packages/dpdk/drivers/net/mlx4/mlx4.c:2437: rxq_del_flow: Assertion `(ibv_destroy_flow(rxq->mac_flow[mac_index][vlan_index])) == 0’ failed.

Aborted (core dumped)

Are there plans to support (and when) secondary mode?

Hi,

I see two potential issues here, I guess this is DPDK 16.07 ?

PMD: mlx5.c:638: mlx5_pci_probe(): no private data for port 0

are you using this tool as a secondary process ? right now our PMD doesn’t fully support secondary process feature

0000:08:00.0 ‘MT27710 Family [ConnectX-4 Lx]’ if=enp8s0f0 drv=mlx5_core unused=igb_uio

How did you configure DPDK to use the Mellanox NIC, Can you also run testpmd and share the segfault ?

Hi -

EAL: RTE Version: ‘DPDK 17.02.0-rc0’

I am trying to use the pdump to test packet capture - I have inconsistent results using tx_pcap - sometime works sometime does not and could not remember which option would make it work

testpmd output:

testpmd -c 0xffe --vdev=eth_pcap0,iface=enp129s0 --vdev=eth_pcap1,iface=enp134s0 – -i --nb-cores=2 --nb-ports=2 --total-num-mbufs=2048

EAL: Detected 32 lcore(s)

EAL: Probing VFIO support…

EAL: PCI device 0000:02:00.0 on NUMA socket 0

EAL: probe driver: 8086:150e net_e1000_igb

EAL: PCI device 0000:02:00.1 on NUMA socket 0

EAL: probe driver: 8086:150e net_e1000_igb

EAL: PCI device 0000:02:00.2 on NUMA socket 0

EAL: probe driver: 8086:150e net_e1000_igb

EAL: PCI device 0000:02:00.3 on NUMA socket 0

EAL: probe driver: 8086:150e net_e1000_igb

EAL: PCI device 0000:81:00.0 on NUMA socket 1

EAL: probe driver: 15b3:1015 net_mlx5

PMD: mlx5.c:419: mlx5_pci_probe(): PCI information matches, using device “mlx5_0” (SR-IOV: false, MPS: true)

PMD: mlx5.c:442: mlx5_pci_probe(): 1 port(s) detected

PMD: mlx5.c:590: mlx5_pci_probe(): port 1 MAC address is e4:1d:2d:c1:66:2c

EAL: PCI device 0000:83:00.0 on NUMA socket 1

EAL: probe driver: 8086:10c9 net_e1000_igb

EAL: PCI device 0000:83:00.1 on NUMA socket 1

EAL: probe driver: 8086:10c9 net_e1000_igb

EAL: PCI device 0000:86:00.0 on NUMA socket 1

EAL: probe driver: 15b3:1015 net_mlx5

PMD: mlx5.c:419: mlx5_pci_probe(): PCI information matches, using device “mlx5_1” (SR-IOV: false, MPS: true)

PMD: mlx5.c:442: mlx5_pci_probe(): 1 port(s) detected

PMD: mlx5.c:590: mlx5_pci_probe(): port 1 MAC address is e4:1d:2d:c1:66:94

PMD: Initializing pmd_pcap for eth_pcap0

PMD: Creating pcap-backed ethdev on numa socket 0

PMD: Initializing pmd_pcap for eth_pcap1

PMD: Creating pcap-backed ethdev on numa socket 0

Interactive-mode selected

USER1: create a new mbuf pool quit