From: Dikshant Chitkara <dchitkara@Airspan.com>
To: "users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Amir Ilan <ailan@Airspan.com>, Veeresh Patil <vpatil@Airspan.com>
Subject: [dpdk-users] DPDK PDUMP Issue
Date: Tue, 14 Jul 2020 08:40:55 +0000 [thread overview]
Message-ID: <db404e78dab84304aa634866928c5448@Airspan.com> (raw)
Hi Team,
We are facing an issue w.r.t to using DPDK PDUMP utility and want to check if you can help us in this regard.
This issue is specific to DPDK 19.05 version or may be newer versions and was not found on DPDK 18.08 version.
The issue is that when we built DPDK in shared library mode and try to run PDUMP we get following error on PDUMP console:
EAL: Failed to hotplug add device
EAL: Error - exiting with code: 1
Cause: vdev creation failed
On Debugging above error message, I found that inside rte_dev_probe() function in the file lib/librte_eal/common/eal_common_dev.c , req.result = -14 which is non-zero value and points to enum EFAULT (Bad address) value, thus leading to above error.
However, when I ran PDUMP in DPDK 18.08, I did not observe any such issue and it worked fine.
DPDK was built with following flags set in config/common_base file:
CONFIG_RTE_LIBRTE_PMD_PCAP=y
CONFIG_RTE_LIBRTE_PDUMP=y
I ran PDUMP with testpmd as primary application and was trying to send some traffic on the Ethernet dpdk port using testpmd and capture it using pdump.
Attached are the logs for both testpmd and pdump in both DPDK19_05 and DPDK_18_08 version for your reference.
Let us know if you can help in this regard.
Thanks,
Dikshant
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pdump_18_08.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: testpmd_18_08.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pdump_19_05.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: testpmd_19_05.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment-0003.txt>
next reply other threads:[~2020-07-17 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 8:40 Dikshant Chitkara [this message]
2020-07-14 16:29 ` [dpdk-users] [dpdk-dev] " Stephen Hemminger
2020-07-22 4:08 ` Varghese, Vipin
2020-07-28 14:51 ` Dikshant Chitkara
2020-07-28 16:23 ` Stephen Hemminger
2020-07-28 16:41 ` Dikshant Chitkara
2020-07-28 17:03 ` Stephen Hemminger
2020-07-28 17:08 ` Dikshant Chitkara
2020-07-29 0:59 ` Varghese, Vipin
2020-07-29 9:14 ` Dikshant Chitkara
2020-07-29 9:51 ` Varghese, Vipin
2020-07-29 9:56 ` Varghese, Vipin
2020-07-29 14:08 ` Dikshant Chitkara
2020-07-30 2:35 ` Varghese, Vipin
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=db404e78dab84304aa634866928c5448@Airspan.com \
--to=dchitkara@airspan.com \
--cc=ailan@Airspan.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.org \
--cc=vpatil@Airspan.com \
/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).