DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: animesh tripathi <anitrip.444@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Error on dpdk 21.08 version
Date: Fri, 10 Sep 2021 10:26:13 +0300	[thread overview]
Message-ID: <20210910102613.601b2016@sovereign> (raw)
In-Reply-To: <CAMH6JP-4i9oCKR-4kiCse-e54DMs2fg2x+kzFOLodkFSmubXdQ@mail.gmail.com>

2021-09-10 10:43 (UTC+0530), animesh tripathi:
> Hi Team,
> 
> I am getting following error while running l2fwd application
> 
> [root@SERVER84 dpdk-21.08]# ./build/examples/dpdk-helloworld
> EAL: Detected 40 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Detected static linkage of DPDK
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: VFIO support initialized
> TELEMETRY: No legacy callbacks, legacy socket not created
> hello from core 0

Is it a complete log or you've just omitted 39 "hello from core ..." messages?
In the latter case there is no error, it's a normal startup sequence.

> 
> After reading through the mailing list I got to know that -d option is used
> pass the drivers path. Even after that I am getting the following error
> message:
> 
> [root@SERVER84 dpdk-21.08]# ./build/examples/dpdk-helloworld -d
> /home/Animesh/DPDK/dpdk-21.08/build/drivers/
> EAL: Detected 40 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Detected static linkage of DPDK
> EAL: RTE_RING tailq is already registered
> PANIC in tailqinitfn_rte_ring_tailq():
> Cannot initialize tailq: RTE_RING
> 16: [./build/examples/dpdk-helloworld() [0xa007cb]]
> 15: [/lib64/libc.so.6(__libc_start_main+0xf5) [0x7ffff4750505]]
> 14: [./build/examples/dpdk-helloworld(main+0x6) [0x53c306]]
> 13: [./build/examples/dpdk-helloworld(rte_eal_init+0x73e) [0xbb563e]]
> 12: [./build/examples/dpdk-helloworld(eal_plugins_init+0x288) [0xba1c18]]
> 11: [/lib64/libdl.so.2(dlopen+0x31) [0x7ffff78d5f81]]
> 10: [/lib64/libdl.so.2(+0x14ed) [0x7ffff78d64ed]]
> 9: [/lib64/ld-linux-x86-64.so.2(+0xf784) [0x7ffff7dea784]]
> 8: [/lib64/libdl.so.2(+0xeeb) [0x7ffff78d5eeb]]
> 7: [/lib64/ld-linux-x86-64.so.2(+0x13b3b) [0x7ffff7deeb3b]]
> 6: [/lib64/ld-linux-x86-64.so.2(+0xf784) [0x7ffff7dea784]]
> 5: [/lib64/ld-linux-x86-64.so.2(+0x1454e) [0x7ffff7def54e]]
> 4: [/lib64/ld-linux-x86-64.so.2(+0xf973) [0x7ffff7dea973]]
> 3:
> [/home/Animesh/DPDK/dpdk-21.08/build/drivers/../lib/librte_ring.so.21(+0xe1c)
> [0x7ffff2d5de1c]]
> 2: [./build/examples/dpdk-helloworld(__rte_panic+0xba) [0x51b664]]
> 1: [./build/examples/dpdk-helloworld(rte_dump_stack+0x1a) [0xbb717a]]
> Aborted (core dumped)
> 
> I will be waiting for your response. Please help me to resolve this issue.

The program has DPDK linked statically, so all the libraries and drivers are
inside the binary. With -d you're trying to load the same code again as
shared libraries, it fails to perform the initialization again.

      reply	other threads:[~2021-09-10  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  5:13 animesh tripathi
2021-09-10  7:26 ` Dmitry Kozlyuk [this message]

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=20210910102613.601b2016@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=anitrip.444@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).