DPDK usage discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Masaru Kawashima <masaru.kawashima.centos@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] HELP: MLX4 problem
Date: Tue, 12 Jan 2016 16:47:04 +0100	[thread overview]
Message-ID: <20160112154704.GE12095@6wind.com> (raw)
In-Reply-To: <CAE-Lg5t680VZchz1q93g-+8rBN+5xAD+NviNyuxKSNgS7zSkTA@mail.gmail.com>

Hi Masaru,

On Tue, Jan 12, 2016 at 06:43:53PM +0900, Masaru Kawashima wrote:
> Hi, all
> 
> I'm trying to use dpdk with Mellanox ConnectX-3.
> But, mlnx4 pmd cannot work fine.
> 
> Following is my environment:
> 
>   OS: CentOS 6.5 (x86_64)
>   Mellanox OFED: MLNX_OFED_LINUX-3.1-1.1.0.1-rhel6.5-x86_64
>   DPDK: MLNX_DPDK-2.1_1.1
> 
> I'm trying to run testpmd, but librte_pmd_mlx4 reports
> "ibv_exp_query_device() failed",
> and EAL reports "No probed ethernet devices".
> 
> What can I do next to work mlx4 pmd fine?
> 
> 
> Following is the testpmd's log:
> 
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Detected lcore 4 as core 4 on socket 0
> EAL: Detected lcore 5 as core 5 on socket 0
> EAL: Detected lcore 6 as core 8 on socket 0
> EAL: Detected lcore 7 as core 9 on socket 0
> EAL: Detected lcore 8 as core 10 on socket 0
> EAL: Detected lcore 9 as core 11 on socket 0
> EAL: Detected lcore 10 as core 12 on socket 0
> EAL: Detected lcore 11 as core 13 on socket 0
> EAL: Detected lcore 12 as core 0 on socket 1
> EAL: Detected lcore 13 as core 1 on socket 1
> EAL: Detected lcore 14 as core 2 on socket 1
> EAL: Detected lcore 15 as core 3 on socket 1
> EAL: Detected lcore 16 as core 4 on socket 1
> EAL: Detected lcore 17 as core 5 on socket 1
> EAL: Detected lcore 18 as core 8 on socket 1
> EAL: Detected lcore 19 as core 9 on socket 1
> EAL: Detected lcore 20 as core 10 on socket 1
> EAL: Detected lcore 21 as core 11 on socket 1
> EAL: Detected lcore 22 as core 12 on socket 1
> EAL: Detected lcore 23 as core 13 on socket 1
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 24 lcore(s)
> EAL: Setting up physically contiguous memory...
> EAL: Ask a virtual area of 0x80000000 bytes
> EAL: Virtual area found at 0x7f2940000000 (size = 0x80000000)
> EAL: Ask a virtual area of 0x80000000 bytes
> EAL: Virtual area found at 0x7f2880000000 (size = 0x80000000)
> EAL: Requesting 2 pages of size 1024MB from socket 0
> EAL: Requesting 2 pages of size 1024MB from socket 1
> EAL: TSC frequency is ~2300002 KHz
> EAL: Master lcore 0 is ready (tid=f6cdc8a0;cpuset=[0])
> EAL: lcore 2 is ready (tid=f58d2700;cpuset=[2])
> EAL: lcore 1 is ready (tid=f62d3700;cpuset=[1])
> EAL: lcore 3 is ready (tid=f4ed1700;cpuset=[3])
> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL:   probe driver: 15b3:1003 librte_pmd_mlx4
> PMD: librte_pmd_mlx4: PCI information matches, using device "mlx4_0" (VF:
> false)
> PMD: librte_pmd_mlx4: 1 port(s) detected
> PMD: librte_pmd_mlx4: ibv_exp_query_device() failed

Make sure ib_uverbs, mlx4_en, mlx4_ib and mlx4_core are all loaded and
coming from Mellanox OFED (normally not the original modules provided by
your Linux distribution), and that you're using an up-to-date firmware
version, although installing MLNX_OFED should have taken care of these
automatically.

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2016-01-12 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  9:43 Masaru Kawashima
2016-01-12 15:47 ` Adrien Mazarguil [this message]
2016-01-14  2:17   ` Masaru Kawashima
2016-01-14 10:04     ` Adrien Mazarguil

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=20160112154704.GE12095@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=masaru.kawashima.centos@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).