Sorry for the duplicate post.

I found the line that returns the error.

In drivers/net/mlx5/mlx5_flow_dv.c, starting at line 6358:
-------------------------------
cache_matcher->matcher_object =
         mlx5_glue->dv_create_flow_matcher(sh->ctx, &dv_attr, tbl->obj);
     if (!cache_matcher->matcher_object) {
         rte_free(cache_matcher);
#ifdef HAVE_MLX5DV_DR
         flow_dv_tbl_resource_release(dev, tbl);
#endif
         return rte_flow_error_set(error, ENOMEM,
                       RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
                       NULL, "cannot create matcher");
     }
-------------------------------
mlx5_glue->dv_create_flow_matcher(...) returns (void *) 0x0.
Because of this, the if-statement is fulfilled and returns the error.

Do you have an idea why the matcher can't be created?

Thanks!
Sebastian

On 03.01.20 11:40, Sebastian Bernauer wrote:
> Hello DPDK team,
>
> I have 2 Mellanox ConnectX-4 MCX415A-CCAT cards connected with DAC (firmware 
> 12.26.4012). Im using debian stretch and DPDK 19.11.
> If i try to start DPDK-applications i get the following error:
>
> sbernauer@he37:~$ lspci | grep Mellanox
> 04:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]
> 42:00.0 Network controller: Mellanox Technologies MT27500 Family [ConnectX-3]
>
> sbernauer@he37:~$ sudo dpdk-19.11/examples/l2fwd/build/app/l2fwd -w 04:00.0 
> -- -p 0x1
> EAL: Detected 40 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: No available hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 15b3:1013 net_mlx5
> MAC updating enabled
> Notice: odd number of ports in portmask.
> Lcore 0: RX port 0
> Initializing port 0... EAL: Error - exiting with code: 1
>    Cause: rte_eth_dev_start:err=-12, port=0
>
> I can't find a description of the error code -12, can you please give my a 
> hint whats my problem?
>
> Thanks a lot!
> Sebastian

Reply via email to