DPDK usage discussions
 help / color / mirror / Atom feed
From: animesh tripathi <anitrip.444@gmail.com>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: running dpdk on mellanox with dpdk 21.08
Date: Tue, 12 Jul 2022 12:05:35 +0530	[thread overview]
Message-ID: <CAMH6JP-tuzy_zNtoL+pKJWfc8DyMHu=j-pQHeNu=x3uh8a+AXQ@mail.gmail.com> (raw)
In-Reply-To: <CAMH6JP8umoU3ho8hB73eGEGTLu1RWVH=R7uXXmhfCLaGmGAvfQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3519 bytes --]

Hi Cliff,

Can you please help me here.

Thanks,
Animesh Tripathi

On Fri, Jul 8, 2022, 4:03 PM animesh tripathi <anitrip.444@gmail.com> wrote:

> Hi Cliff,
>
> The earlier error is resolved now. It was some compilation problem. Now I
> am getting some other error:
>
> EAL: Detected 24 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Auto-detected process type: PRIMARY
> EAL: Detected static linkage of DPDK
> EAL: Multi-process socket /var/run/dpdk/nr_dpdk/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: VFIO support initialized
> TELEMETRY: No legacy callbacks, legacy socket not created
> EAL: Driver cannot attach the device (0000:b5:00.1)
> EAL: Failed to attach device on primary process
> PANIC in nr_dpdk_init():
> Network port doesn't exist.6: [./a() [0xbba5aa]]
> 5: [/usr/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)
> [0x7f7d0fae40b3]]
> 4: [./a(main+0x428) [0x7476e8]]
> 3: [./a() [0x55b885]]
> 2: [./a(__rte_panic+0xcd) [0x7409a7]]
> 1: [./a(rte_dump_stack+0x32) [0x13a47a2]]\
>
> These are the mellanox drivers installed on my machine:
> mlx5_ib               393216  0
> mlx5_core            1552384  1 mlx5_ib
> mlxdevm               172032  1 mlx5_core
> auxiliary              16384  2 mlx5_ib,mlx5_core
> ib_uverbs             135168  2 rdma_ucm,mlx5_ib
> tls                    73728  1 mlx5_core
> mlxfw                  32768  1 mlx5_core
> psample                20480  1 mlx5_core
> ib_core               319488  9
> rdma_cm,ib_ipoib,nvidia_peermem,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
> mlx_compat             65536  12
> rdma_cm,ib_ipoib,mlxdevm,iw_cm,auxiliary,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
> pci_hyperv_intf        16384  1 mlx5_core
>
> Can you please help me in resolving this error.
>
> Thanks,
> Animesh Tripathi
>
>
> On Fri, Jul 8, 2022 at 11:42 AM animesh tripathi <anitrip.444@gmail.com>
> wrote:
>
>> Hi Cliff,
>>
>> Yes I am running as root
>>
>> Thanks,
>> Animesh Tripathi
>>
>> On Fri, Jul 8, 2022, 10:29 AM animesh tripathi <anitrip.444@gmail.com>
>> wrote:
>>
>>> Hi Cliff,
>>>
>>> Please find the output of meson command.
>>>
>>> Thanks,
>>> Animesh Tripathi
>>>
>>> On Thu, Jul 7, 2022 at 8:17 PM Cliff Burdick <shaklee3@gmail.com> wrote:
>>>
>>>> Please paste the output of the meson command. Are you running as root?
>>>>
>>>>
>>>> On Thu, Jul 7, 2022, 06:13 animesh tripathi <anitrip.444@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Team,
>>>>>
>>>>> I have to run dpdk on mellanox nic. I have compiled dpdk 21.08 with
>>>>> the following commands:
>>>>>
>>>>> meson --prefix=$(pwd)/build build
>>>>> ninja -C build
>>>>> ninja -C build install
>>>>> ldconfig
>>>>>
>>>>> While running the application I am getting following error:
>>>>>
>>>>> EAL: Detected 24 lcore(s)
>>>>> EAL: Detected 1 NUMA nodes
>>>>> EAL: Auto-detected process type: PRIMARY
>>>>> EAL: Detected static linkage of DPDK
>>>>> EAL: failed to parse device "0000:b5:00.1"
>>>>> EAL: Unable to parse device '0000:b5:00.1'
>>>>> PANIC in nr_dpdk_init():
>>>>> Cannot init EAL: No such device
>>>>> 6: [./a() [0x444179]]
>>>>> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)
>>>>> [0x7f08e0f2e0b3]]
>>>>> 4: [./a(main+0x428) [0x4431f8]]
>>>>> 3: [./a(nr_dpdk_init+0x268) [0x509bd8]]
>>>>> 2: [./a(__rte_panic+0xcd) [0x43c55e]]
>>>>> 1: [./a(rte_dump_stack+0x32) [0x539ed2]]
>>>>>
>>>>> Also I cannot find mlx5 compiled libs in the dpdk build folder. Please
>>>>> help me in resolving this issue.
>>>>>
>>>>> Thanks,
>>>>> Animesh Tripathi
>>>>>
>>>>

[-- Attachment #2: Type: text/html, Size: 5997 bytes --]

  reply	other threads:[~2022-07-12  6:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 13:12 animesh tripathi
2022-07-07 14:46 ` Cliff Burdick
2022-07-08  4:59   ` animesh tripathi
2022-07-08  6:12     ` animesh tripathi
2022-07-08 10:33       ` animesh tripathi
2022-07-12  6:35         ` animesh tripathi [this message]
2022-07-15 22:20           ` Cliff Burdick

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='CAMH6JP-tuzy_zNtoL+pKJWfc8DyMHu=j-pQHeNu=x3uh8a+AXQ@mail.gmail.com' \
    --to=anitrip.444@gmail.com \
    --cc=shaklee3@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).