DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
@ 2021-01-28  5:49 Pravein GK
  2021-01-28  8:22 ` Raslan Darawsheh
  0 siblings, 1 reply; 7+ messages in thread
From: Pravein GK @ 2021-01-28  5:49 UTC (permalink / raw)
  To: users

Hello All,

I am using DPDK 20.08 with Mellanox Connect X 5 NICs.
I have installed the latest OFED drivers with "--dpdk --upstream-libs".
However, while launching a dpdk application, I get the below error :

EAL: Detected 24 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:   Invalid NUMA socket, default to 0
>
>
> *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.0 (socket
> 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.0, are kernel
> drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> EAL: Requested device 0000:1f:00.0 cannot be used
> EAL:   Invalid NUMA socket, default to 0
>
>
> *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.1 (socket
> 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.1, are kernel
> drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> EAL: Requested device 0000:1f:00.1 cannot be used
> EAL: No legacy callbacks, legacy socket not created
> EAL: Error - exiting with code: 1
>   Cause: Cannot create mbuf pool , error=Invalid argument


I am stuck with this error, and unable to proceed for a long time despite
trying most of the things suggested in forums. Please help.

Thanks,
Pravein

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
  2021-01-28  5:49 [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error Pravein GK
@ 2021-01-28  8:22 ` Raslan Darawsheh
  2021-01-28  8:36   ` Pravein GK
  0 siblings, 1 reply; 7+ messages in thread
From: Raslan Darawsheh @ 2021-01-28  8:22 UTC (permalink / raw)
  To: Pravein GK, users

Hi Parvein, 

Can you kindly confirm that the kernel drivers (mlx5_ib, mlx5_core) are loaded? 
(lsmod | grep mlx5_)

If not please try to restart the kernel driver:

/etc/init.d/openibd force-restart 

Kindest regards,
Raslan Darawsheh

> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Pravein GK
> Sent: Thursday, January 28, 2021 7:49 AM
> To: users@dpdk.org
> Subject: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
> 
> Hello All,
> 
> I am using DPDK 20.08 with Mellanox Connect X 5 NICs.
> I have installed the latest OFED drivers with "--dpdk --upstream-libs".
> However, while launching a dpdk application, I get the below error :
> 
> EAL: Detected 24 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:   Invalid NUMA socket, default to 0
> >
> >
> > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.0 (socket
> > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.0, are kernel
> > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > EAL: Requested device 0000:1f:00.0 cannot be used
> > EAL:   Invalid NUMA socket, default to 0
> >
> >
> > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.1 (socket
> > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.1, are kernel
> > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > EAL: Requested device 0000:1f:00.1 cannot be used
> > EAL: No legacy callbacks, legacy socket not created
> > EAL: Error - exiting with code: 1
> >   Cause: Cannot create mbuf pool , error=Invalid argument
> 
> 
> I am stuck with this error, and unable to proceed for a long time despite
> trying most of the things suggested in forums. Please help.
> 
> Thanks,
> Pravein

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
  2021-01-28  8:22 ` Raslan Darawsheh
@ 2021-01-28  8:36   ` Pravein GK
  2021-01-28  8:39     ` Raslan Darawsheh
  0 siblings, 1 reply; 7+ messages in thread
From: Pravein GK @ 2021-01-28  8:36 UTC (permalink / raw)
  To: Raslan Darawsheh; +Cc: users

Hi Raslan,

Thanks for your reply.

The lsmod o/p is below :

$ lsmod | grep mlx5_
mlx5_ib               364544  0
ib_uverbs             131072  2 rdma_ucm,mlx5_ib
mlx5_core            1294336  1 mlx5_ib
mlxfw                  24576  1 mlx5_core
psample                20480  1 mlx5_core
devlink                45056  1 mlx5_core
ib_core               311296  8
rdma_cm,ib_ipoib,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
mlx_compat             45056  10
rdma_cm,ib_ipoib,iw_cm,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
ptp                    20480  1 mlx5_core

I had tried the force restart, and even after that , I get the same error.

Thanks,
Pravein



On Thu, Jan 28, 2021 at 1:52 PM Raslan Darawsheh <rasland@nvidia.com> wrote:

> Hi Parvein,
>
> Can you kindly confirm that the kernel drivers (mlx5_ib, mlx5_core) are
> loaded?
> (lsmod | grep mlx5_)
>
> If not please try to restart the kernel driver:
>
> /etc/init.d/openibd force-restart
>
> Kindest regards,
> Raslan Darawsheh
>
> > -----Original Message-----
> > From: users <users-bounces@dpdk.org> On Behalf Of Pravein GK
> > Sent: Thursday, January 28, 2021 7:49 AM
> > To: users@dpdk.org
> > Subject: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
> >
> > Hello All,
> >
> > I am using DPDK 20.08 with Mellanox Connect X 5 NICs.
> > I have installed the latest OFED drivers with "--dpdk --upstream-libs".
> > However, while launching a dpdk application, I get the below error :
> >
> > EAL: Detected 24 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:   Invalid NUMA socket, default to 0
> > >
> > >
> > > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.0
> (socket
> > > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.0, are kernel
> > > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > > EAL: Requested device 0000:1f:00.0 cannot be used
> > > EAL:   Invalid NUMA socket, default to 0
> > >
> > >
> > > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.1
> (socket
> > > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.1, are kernel
> > > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > > EAL: Requested device 0000:1f:00.1 cannot be used
> > > EAL: No legacy callbacks, legacy socket not created
> > > EAL: Error - exiting with code: 1
> > >   Cause: Cannot create mbuf pool , error=Invalid argument
> >
> >
> > I am stuck with this error, and unable to proceed for a long time despite
> > trying most of the things suggested in forums. Please help.
> >
> > Thanks,
> > Pravein
>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
  2021-01-28  8:36   ` Pravein GK
@ 2021-01-28  8:39     ` Raslan Darawsheh
  2021-01-28  9:02       ` Pravein GK
  0 siblings, 1 reply; 7+ messages in thread
From: Raslan Darawsheh @ 2021-01-28  8:39 UTC (permalink / raw)
  To: Pravein GK; +Cc: users

Hi Pravein,

Do you happen to have any errors in dmesg output ?
Also, can you post the output of ibdev2netdev ?

Kindest regards,
Raslan Darawsheh

From: Pravein GK <praveingk@gmail.com>
Sent: Thursday, January 28, 2021 10:36 AM
To: Raslan Darawsheh <rasland@nvidia.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error

Hi Raslan,

Thanks for your reply.

The lsmod o/p is below :

$ lsmod | grep mlx5_
mlx5_ib               364544  0
ib_uverbs             131072  2 rdma_ucm,mlx5_ib
mlx5_core            1294336  1 mlx5_ib
mlxfw                  24576  1 mlx5_core
psample                20480  1 mlx5_core
devlink                45056  1 mlx5_core
ib_core               311296  8 rdma_cm,ib_ipoib,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
mlx_compat             45056  10 rdma_cm,ib_ipoib,iw_cm,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
ptp                    20480  1 mlx5_core

I had tried the force restart, and even after that , I get the same error.

Thanks,
Pravein



On Thu, Jan 28, 2021 at 1:52 PM Raslan Darawsheh <rasland@nvidia.com<mailto:rasland@nvidia.com>> wrote:
Hi Parvein,

Can you kindly confirm that the kernel drivers (mlx5_ib, mlx5_core) are loaded?
(lsmod | grep mlx5_)

If not please try to restart the kernel driver:

/etc/init.d/openibd force-restart

Kindest regards,
Raslan Darawsheh

> -----Original Message-----
> From: users <users-bounces@dpdk.org<mailto:users-bounces@dpdk.org>> On Behalf Of Pravein GK
> Sent: Thursday, January 28, 2021 7:49 AM
> To: users@dpdk.org<mailto:users@dpdk.org>
> Subject: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
>
> Hello All,
>
> I am using DPDK 20.08 with Mellanox Connect X 5 NICs.
> I have installed the latest OFED drivers with "--dpdk --upstream-libs".
> However, while launching a dpdk application, I get the below error :
>
> EAL: Detected 24 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:   Invalid NUMA socket, default to 0
> >
> >
> > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.0 (socket
> > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.0, are kernel
> > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > EAL: Requested device 0000:1f:00.0 cannot be used
> > EAL:   Invalid NUMA socket, default to 0
> >
> >
> > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.1 (socket
> > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.1, are kernel
> > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > EAL: Requested device 0000:1f:00.1 cannot be used
> > EAL: No legacy callbacks, legacy socket not created
> > EAL: Error - exiting with code: 1
> >   Cause: Cannot create mbuf pool , error=Invalid argument
>
>
> I am stuck with this error, and unable to proceed for a long time despite
> trying most of the things suggested in forums. Please help.
>
> Thanks,
> Pravein

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
  2021-01-28  8:39     ` Raslan Darawsheh
@ 2021-01-28  9:02       ` Pravein GK
  2021-02-02  7:50         ` Pravein GK
  0 siblings, 1 reply; 7+ messages in thread
From: Pravein GK @ 2021-01-28  9:02 UTC (permalink / raw)
  To: Raslan Darawsheh; +Cc: users

I did not happen to see any errors in dmesg.

Please find the dmesg, and ibdev2netdev attached.

Thanks,
Pravein

On Thu, Jan 28, 2021 at 2:09 PM Raslan Darawsheh <rasland@nvidia.com> wrote:

> Hi Pravein,
>
>
>
> Do you happen to have any errors in dmesg output ?
>
> Also, can you post the output of ibdev2netdev ?
>
>
>
> Kindest regards,
>
> Raslan Darawsheh
>
>
>
> *From:* Pravein GK <praveingk@gmail.com>
> *Sent:* Thursday, January 28, 2021 10:36 AM
> *To:* Raslan Darawsheh <rasland@nvidia.com>
> *Cc:* users@dpdk.org
> *Subject:* Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5
> Error
>
>
>
> Hi Raslan,
>
>
>
> Thanks for your reply.
>
>
>
> The lsmod o/p is below :
>
>
>
> $ lsmod | grep mlx5_
> mlx5_ib               364544  0
> ib_uverbs             131072  2 rdma_ucm,mlx5_ib
> mlx5_core            1294336  1 mlx5_ib
> mlxfw                  24576  1 mlx5_core
> psample                20480  1 mlx5_core
> devlink                45056  1 mlx5_core
> ib_core               311296  8
> rdma_cm,ib_ipoib,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
> mlx_compat             45056  10
> rdma_cm,ib_ipoib,iw_cm,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
> ptp                    20480  1 mlx5_core
>
>
>
> I had tried the force restart, and even after that , I get the same error.
>
>
>
> Thanks,
>
> Pravein
>
>
>
>
>
>
>
> On Thu, Jan 28, 2021 at 1:52 PM Raslan Darawsheh <rasland@nvidia.com>
> wrote:
>
> Hi Parvein,
>
> Can you kindly confirm that the kernel drivers (mlx5_ib, mlx5_core) are
> loaded?
> (lsmod | grep mlx5_)
>
> If not please try to restart the kernel driver:
>
> /etc/init.d/openibd force-restart
>
> Kindest regards,
> Raslan Darawsheh
>
> > -----Original Message-----
> > From: users <users-bounces@dpdk.org> On Behalf Of Pravein GK
> > Sent: Thursday, January 28, 2021 7:49 AM
> > To: users@dpdk.org
> > Subject: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
> >
> > Hello All,
> >
> > I am using DPDK 20.08 with Mellanox Connect X 5 NICs.
> > I have installed the latest OFED drivers with "--dpdk --upstream-libs".
> > However, while launching a dpdk application, I get the below error :
> >
> > EAL: Detected 24 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:   Invalid NUMA socket, default to 0
> > >
> > >
> > > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.0
> (socket
> > > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.0, are kernel
> > > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > > EAL: Requested device 0000:1f:00.0 cannot be used
> > > EAL:   Invalid NUMA socket, default to 0
> > >
> > >
> > > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.1
> (socket
> > > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.1, are kernel
> > > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > > EAL: Requested device 0000:1f:00.1 cannot be used
> > > EAL: No legacy callbacks, legacy socket not created
> > > EAL: Error - exiting with code: 1
> > >   Cause: Cannot create mbuf pool , error=Invalid argument
> >
> >
> > I am stuck with this error, and unable to proceed for a long time despite
> > trying most of the things suggested in forums. Please help.
> >
> > Thanks,
> > Pravein
>
>
-------------- next part --------------
 dmesg | grep mlx
[    5.520063] mlx_compat: loading out-of-tree module taints kernel.
[    5.539232] mlx_compat: loading out-of-tree module taints kernel.
[    5.582962] mlx_compat: module verification failed: signature and/or required key missing - tainting kernel
[    5.903950] mlx5_core 0000:1f:00.0: enabling device (0040 -> 0042)
[    5.941666] mlx5_core 0000:1f:00.0: firmware version: 16.29.1016
[    5.941692] mlx5_core 0000:1f:00.0: 64.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x16 link at 0000:00:07.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)
[    6.200500] mlx5_core 0000:1f:00.0: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps
[    6.200639] mlx5_core 0000:1f:00.0: E-Switch: Total vports 66, per vport: max uc(1024) max mc(16384)
[    6.206971] mlx5_core 0000:1f:00.0: Port module event: module 0, Cable plugged
[    6.207523] mlx5_core 0000:1f:00.0: mlx5_pcie_event:302:(pid 250): PCIe slot advertised sufficient power (27W).
[    6.215561] mlx5_core 0000:1f:00.0: mlx5_fw_tracer_start:815:(pid 336): FWTracer: Ownership granted and active
[    6.223151] mlx5_core 0000:1f:00.1: enabling device (0040 -> 0042)
[    6.223891] mlx5_core 0000:1f:00.1: firmware version: 16.29.1016
[    6.223953] mlx5_core 0000:1f:00.1: 64.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x16 link at 0000:00:07.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)
[    6.494022] mlx5_core 0000:1f:00.1: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps
[    6.494269] mlx5_core 0000:1f:00.1: E-Switch: Total vports 66, per vport: max uc(1024) max mc(16384)
[    6.502335] mlx5_core 0000:1f:00.1: Port module event: module 1, Cable plugged
[    6.502778] mlx5_core 0000:1f:00.1: mlx5_pcie_event:302:(pid 399): PCIe slot advertised sufficient power (27W).
[    6.519079] mlx5_core 0000:1f:00.0: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0)
[    6.774159] mlx5_core 0000:1f:00.0: Supported tc offload range - chains: 4294967294, prios: 4294967295
[    6.790042] mlx5_core 0000:1f:00.1: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0)
[    7.020323] mlx5_core 0000:1f:00.1: Supported tc offload range - chains: 4294967294, prios: 4294967295
[    7.037677] mlx5_core 0000:1f:00.1 ens3f1: renamed from eth1
[    7.084399] mlx5_core 0000:1f:00.0 ens3f0: renamed from eth0
[ 3204.024443] mlx5_core 0000:1f:00.1: mlx5_fw_tracer_start:815:(pid 450): FWTracer: Ownership granted and active
[ 3204.942979] mlx5_core 0000:1f:00.0: E-Switch: cleanup
[ 3209.991140] mlx5_core 0000:1f:00.1: E-Switch: cleanup
[ 4360.255008] mlx5_core 0000:1f:00.0: firmware version: 16.29.1016
[ 4360.255037] mlx5_core 0000:1f:00.0: 64.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x16 link at 0000:00:07.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)
[ 4360.509355] mlx5_core 0000:1f:00.0: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps
[ 4360.509473] mlx5_core 0000:1f:00.0: E-Switch: Total vports 66, per vport: max uc(1024) max mc(16384)
[ 4360.517582] mlx5_core 0000:1f:00.0: Port module event: module 0, Cable plugged
[ 4360.518581] mlx5_core 0000:1f:00.0: mlx5_pcie_event:302:(pid 450): PCIe slot advertised sufficient power (27W).
[ 4360.526609] mlx5_core 0000:1f:00.0: mlx5_fw_tracer_start:815:(pid 2646): FWTracer: Ownership granted and active
[ 4360.534803] mlx5_core 0000:1f:00.0: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0)
[ 4360.765688] mlx5_core 0000:1f:00.0: Supported tc offload range - chains: 4294967294, prios: 4294967295
[ 4360.779786] mlx5_core 0000:1f:00.0 ens3f0: renamed from eth0
[ 4362.947189] mlx5_core 0000:1f:00.1: firmware version: 16.29.1016
[ 4362.947221] mlx5_core 0000:1f:00.1: 64.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x16 link at 0000:00:07.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)
[ 4363.214633] mlx5_core 0000:1f:00.1: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps
[ 4363.214754] mlx5_core 0000:1f:00.1: E-Switch: Total vports 66, per vport: max uc(1024) max mc(16384)
[ 4363.223401] mlx5_core 0000:1f:00.1: Port module event: module 1, Cable plugged
[ 4363.223695] mlx5_core 0000:1f:00.1: mlx5_pcie_event:302:(pid 2720): PCIe slot advertised sufficient power (27W).
[ 4363.237643] mlx5_core 0000:1f:00.1: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0)
[ 4363.466358] mlx5_core 0000:1f:00.1: Supported tc offload range - chains: 4294967294, prios: 4294967295
[ 4363.480310] mlx5_core 0000:1f:00.1 ens3f1: renamed from eth0
[ 4376.198303] mlx5_core 0000:1f:00.1: mlx5_fw_tracer_start:815:(pid 5): FWTracer: Ownership granted and active
[ 4377.248797] mlx5_core 0000:1f:00.0: E-Switch: cleanup
[ 4381.736724] mlx5_core 0000:1f:00.1: E-Switch: cleanup
[ 5127.246120] mlx5_core 0000:1f:00.0: firmware version: 16.29.1016
[ 5127.246148] mlx5_core 0000:1f:00.0: 64.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x16 link at 0000:00:07.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)
[ 5127.500888] mlx5_core 0000:1f:00.0: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps
[ 5127.501005] mlx5_core 0000:1f:00.0: E-Switch: Total vports 66, per vport: max uc(1024) max mc(16384)
[ 5127.508938] mlx5_core 0000:1f:00.0: Port module event: module 0, Cable plugged
[ 5127.509728] mlx5_core 0000:1f:00.0: mlx5_pcie_event:302:(pid 5): PCIe slot advertised sufficient power (27W).
[ 5127.517387] mlx5_core 0000:1f:00.0: mlx5_fw_tracer_start:815:(pid 29725): FWTracer: Ownership granted and active
[ 5127.524704] mlx5_core 0000:1f:00.0: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0)
[ 5127.746557] mlx5_core 0000:1f:00.0: Supported tc offload range - chains: 4294967294, prios: 4294967295
[ 5127.762118] mlx5_core 0000:1f:00.0 ens3f0: renamed from eth0
[16520.222993] mlx5_core 0000:1f:00.0: E-Switch: cleanup
[16524.824892] mlx5_core 0000:1f:00.0: firmware version: 16.29.1016
[16524.824917] mlx5_core 0000:1f:00.0: 64.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x16 link at 0000:00:07.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)
[16525.075910] mlx5_core 0000:1f:00.0: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps
[16525.076021] mlx5_core 0000:1f:00.0: E-Switch: Total vports 66, per vport: max uc(1024) max mc(16384)
[16525.083206] mlx5_core 0000:1f:00.0: Port module event: module 0, Cable plugged
[16525.083542] mlx5_core 0000:1f:00.0: mlx5_pcie_event:302:(pid 5): PCIe slot advertised sufficient power (27W).
[16525.091017] mlx5_core 0000:1f:00.0: mlx5_fw_tracer_start:815:(pid 2850): FWTracer: Ownership granted and active
[16525.099705] mlx5_core 0000:1f:00.0: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0)
[16525.338241] mlx5_core 0000:1f:00.0: Supported tc offload range - chains: 4294967294, prios: 4294967295
[16525.353781] mlx5_core 0000:1f:00.0 ens3f0: renamed from eth0
[16547.184865] mlx5_core 0000:1f:00.0 ens3f0: Link down
[16557.216630] mlx5_core 0000:1f:00.0 ens3f0: Link up

$ ibdev2netdev
mlx5_0 port 1 ==> ens3f0 (Up)


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
  2021-01-28  9:02       ` Pravein GK
@ 2021-02-02  7:50         ` Pravein GK
  2021-02-02  8:29           ` Raslan Darawsheh
  0 siblings, 1 reply; 7+ messages in thread
From: Pravein GK @ 2021-02-02  7:50 UTC (permalink / raw)
  To: Raslan Darawsheh; +Cc: users

I am still facing this issue, and stuck without knowing how to proceed.
Appreciate any help available.

Thanks,
Pravein

On Thu, Jan 28, 2021 at 2:32 PM Pravein GK <praveingk@gmail.com> wrote:

> I did not happen to see any errors in dmesg.
>
> Please find the dmesg, and ibdev2netdev attached.
>
> Thanks,
> Pravein
>
> On Thu, Jan 28, 2021 at 2:09 PM Raslan Darawsheh <rasland@nvidia.com>
> wrote:
>
>> Hi Pravein,
>>
>>
>>
>> Do you happen to have any errors in dmesg output ?
>>
>> Also, can you post the output of ibdev2netdev ?
>>
>>
>>
>> Kindest regards,
>>
>> Raslan Darawsheh
>>
>>
>>
>> *From:* Pravein GK <praveingk@gmail.com>
>> *Sent:* Thursday, January 28, 2021 10:36 AM
>> *To:* Raslan Darawsheh <rasland@nvidia.com>
>> *Cc:* users@dpdk.org
>> *Subject:* Re: [dpdk-users] common_mlx5: Failed to load driver =
>> net_mlx5 Error
>>
>>
>>
>> Hi Raslan,
>>
>>
>>
>> Thanks for your reply.
>>
>>
>>
>> The lsmod o/p is below :
>>
>>
>>
>> $ lsmod | grep mlx5_
>> mlx5_ib               364544  0
>> ib_uverbs             131072  2 rdma_ucm,mlx5_ib
>> mlx5_core            1294336  1 mlx5_ib
>> mlxfw                  24576  1 mlx5_core
>> psample                20480  1 mlx5_core
>> devlink                45056  1 mlx5_core
>> ib_core               311296  8
>> rdma_cm,ib_ipoib,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
>> mlx_compat             45056  10
>> rdma_cm,ib_ipoib,iw_cm,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
>> ptp                    20480  1 mlx5_core
>>
>>
>>
>> I had tried the force restart, and even after that , I get the same error.
>>
>>
>>
>> Thanks,
>>
>> Pravein
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Jan 28, 2021 at 1:52 PM Raslan Darawsheh <rasland@nvidia.com>
>> wrote:
>>
>> Hi Parvein,
>>
>> Can you kindly confirm that the kernel drivers (mlx5_ib, mlx5_core) are
>> loaded?
>> (lsmod | grep mlx5_)
>>
>> If not please try to restart the kernel driver:
>>
>> /etc/init.d/openibd force-restart
>>
>> Kindest regards,
>> Raslan Darawsheh
>>
>> > -----Original Message-----
>> > From: users <users-bounces@dpdk.org> On Behalf Of Pravein GK
>> > Sent: Thursday, January 28, 2021 7:49 AM
>> > To: users@dpdk.org
>> > Subject: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5
>> Error
>> >
>> > Hello All,
>> >
>> > I am using DPDK 20.08 with Mellanox Connect X 5 NICs.
>> > I have installed the latest OFED drivers with "--dpdk --upstream-libs".
>> > However, while launching a dpdk application, I get the below error :
>> >
>> > EAL: Detected 24 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:   Invalid NUMA socket, default to 0
>> > >
>> > >
>> > > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.0
>> (socket
>> > > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.0, are
>> kernel
>> > > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
>> > > EAL: Requested device 0000:1f:00.0 cannot be used
>> > > EAL:   Invalid NUMA socket, default to 0
>> > >
>> > >
>> > > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.1
>> (socket
>> > > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.1, are
>> kernel
>> > > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
>> > > EAL: Requested device 0000:1f:00.1 cannot be used
>> > > EAL: No legacy callbacks, legacy socket not created
>> > > EAL: Error - exiting with code: 1
>> > >   Cause: Cannot create mbuf pool , error=Invalid argument
>> >
>> >
>> > I am stuck with this error, and unable to proceed for a long time
>> despite
>> > trying most of the things suggested in forums. Please help.
>> >
>> > Thanks,
>> > Pravein
>>
>>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
  2021-02-02  7:50         ` Pravein GK
@ 2021-02-02  8:29           ` Raslan Darawsheh
  0 siblings, 0 replies; 7+ messages in thread
From: Raslan Darawsheh @ 2021-02-02  8:29 UTC (permalink / raw)
  To: Pravein GK, NBU-SupportAdmin; +Cc: users

@Mellanox Support Admin<mailto:supportadmin@mellanox.com>
Hi Pravein,

Sorry for late response, but can you kindly have this with support admin?
I guess it might require some debug session to be able to identify the root cause for it.

Kindest regards,
Raslan Darawsheh

From: Pravein GK <praveingk@gmail.com>
Sent: Tuesday, February 2, 2021 9:51 AM
To: Raslan Darawsheh <rasland@nvidia.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error

I am still facing this issue, and stuck without knowing how to proceed.
Appreciate any help available.

Thanks,
Pravein

On Thu, Jan 28, 2021 at 2:32 PM Pravein GK <praveingk@gmail.com<mailto:praveingk@gmail.com>> wrote:
I did not happen to see any errors in dmesg.

Please find the dmesg, and ibdev2netdev attached.

Thanks,
Pravein

On Thu, Jan 28, 2021 at 2:09 PM Raslan Darawsheh <rasland@nvidia.com<mailto:rasland@nvidia.com>> wrote:
Hi Pravein,

Do you happen to have any errors in dmesg output ?
Also, can you post the output of ibdev2netdev ?

Kindest regards,
Raslan Darawsheh

From: Pravein GK <praveingk@gmail.com<mailto:praveingk@gmail.com>>
Sent: Thursday, January 28, 2021 10:36 AM
To: Raslan Darawsheh <rasland@nvidia.com<mailto:rasland@nvidia.com>>
Cc: users@dpdk.org<mailto:users@dpdk.org>
Subject: Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error

Hi Raslan,

Thanks for your reply.

The lsmod o/p is below :

$ lsmod | grep mlx5_
mlx5_ib               364544  0
ib_uverbs             131072  2 rdma_ucm,mlx5_ib
mlx5_core            1294336  1 mlx5_ib
mlxfw                  24576  1 mlx5_core
psample                20480  1 mlx5_core
devlink                45056  1 mlx5_core
ib_core               311296  8 rdma_cm,ib_ipoib,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
mlx_compat             45056  10 rdma_cm,ib_ipoib,iw_cm,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
ptp                    20480  1 mlx5_core

I had tried the force restart, and even after that , I get the same error.

Thanks,
Pravein



On Thu, Jan 28, 2021 at 1:52 PM Raslan Darawsheh <rasland@nvidia.com<mailto:rasland@nvidia.com>> wrote:
Hi Parvein,

Can you kindly confirm that the kernel drivers (mlx5_ib, mlx5_core) are loaded?
(lsmod | grep mlx5_)

If not please try to restart the kernel driver:

/etc/init.d/openibd force-restart

Kindest regards,
Raslan Darawsheh

> -----Original Message-----
> From: users <users-bounces@dpdk.org<mailto:users-bounces@dpdk.org>> On Behalf Of Pravein GK
> Sent: Thursday, January 28, 2021 7:49 AM
> To: users@dpdk.org<mailto:users@dpdk.org>
> Subject: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
>
> Hello All,
>
> I am using DPDK 20.08 with Mellanox Connect X 5 NICs.
> I have installed the latest OFED drivers with "--dpdk --upstream-libs".
> However, while launching a dpdk application, I get the below error :
>
> EAL: Detected 24 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:   Invalid NUMA socket, default to 0
> >
> >
> > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.0 (socket
> > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.0, are kernel
> > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > EAL: Requested device 0000:1f:00.0 cannot be used
> > EAL:   Invalid NUMA socket, default to 0
> >
> >
> > *EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:1f:00.1 (socket
> > 0)net_mlx5: no Verbs device matches PCI device 0000:1f:00.1, are kernel
> > drivers loaded?common_mlx5: Failed to load driver = net_mlx5.*
> > EAL: Requested device 0000:1f:00.1 cannot be used
> > EAL: No legacy callbacks, legacy socket not created
> > EAL: Error - exiting with code: 1
> >   Cause: Cannot create mbuf pool , error=Invalid argument
>
>
> I am stuck with this error, and unable to proceed for a long time despite
> trying most of the things suggested in forums. Please help.
>
> Thanks,
> Pravein

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-02-02  8:29 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-28  5:49 [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error Pravein GK
2021-01-28  8:22 ` Raslan Darawsheh
2021-01-28  8:36   ` Pravein GK
2021-01-28  8:39     ` Raslan Darawsheh
2021-01-28  9:02       ` Pravein GK
2021-02-02  7:50         ` Pravein GK
2021-02-02  8:29           ` Raslan Darawsheh

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git