From: Raslan Darawsheh <rasland@nvidia.com>
To: Pravein GK <praveingk@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] common_mlx5: Failed to load driver = net_mlx5 Error
Date: Thu, 28 Jan 2021 08:22:44 +0000 [thread overview]
Message-ID: <DM6PR12MB27484BC788844C31071D9055CFBA9@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAE4=sScOFnFfX970UBHUyaO4f+_zD=JepsT2d1uCVirzATwNTQ@mail.gmail.com>
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 prev parent reply other threads:[~2021-01-28 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 5:49 Pravein GK
2021-01-28 8:22 ` Raslan Darawsheh [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM6PR12MB27484BC788844C31071D9055CFBA9@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=praveingk@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).