From: Srinivas Kotamarti <srinivas_kotamarti@affirmednetworks.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] issues with dpdk-pdump
Date: Thu, 18 Oct 2018 21:34:52 +0000 [thread overview]
Message-ID: <8A47B1032B7A634D8DEF55F102DE2C9BC089363F@MBX021-E5-VA-2.exch021.domain.local> (raw)
Hello,
I want to use dpdk-pdump for packet capture. As explained in the http://doc.dpdk.org/guides/tools/pdump.html http://doc.dpdk.org/guides/prog_guide/pdump_lib.html I have compiled the DPDK with CONFIG_RTE_LIBRTE_PMD_PCAP=y and modified my application to initialize the pdump PMD by calling the rte_pdump_init()
I am invoking the dpdk-pdump as follows
/opt/thoroughbred/dpdk/tools/dpdk-pdump -- --pdump 'port=0, queue=*, rx-dev=/boot/partitions/storage/tosfp-pt-dpdk-untrack-fail-00rxtx.01none.02none.03none.pcapng, tx-dev=/boot/partitions/storage/tosfp-pt-dpdk-untrack-fail-00rxtx.01none.02none.03none.pcapng' &
It crashes with the following trace
EAL: Detected 7 lcore(s)
EAL: Detected 1 NUMA nodes
PANIC in rte_eal_config_attach():
Cannot open '/var/run/.rte_config' for rte_mem_config
6: [/opt/thoroughbred/dpdk/tools/dpdk-pdump() [0x464e51]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f801e50eb45]]
4: [/opt/thoroughbred/dpdk/tools/dpdk-pdump(main+0xeb) [0x45d43b]]
3: [/opt/thoroughbred/dpdk/tools/dpdk-pdump(rte_eal_init+0xde7) [0x4d2527]]
2: [/opt/thoroughbred/dpdk/tools/dpdk-pdump(__rte_panic+0xba) [0x45524d]]
1: [/opt/thoroughbred/dpdk/tools/dpdk-pdump(rte_dump_stack+0x18) [0x4dc928]]
What am I doing wrong?
Thanks
--Srinias
next reply other threads:[~2018-10-18 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 21:34 Srinivas Kotamarti [this message]
2018-10-20 12:55 ` Rami Rosen
2018-10-22 20:49 ` Srinivas Kotamarti
2018-10-24 5:11 ` Rami Rosen
2018-10-22 5:39 ` Gowrishankar Muthukrishnan
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=8A47B1032B7A634D8DEF55F102DE2C9BC089363F@MBX021-E5-VA-2.exch021.domain.local \
--to=srinivas_kotamarti@affirmednetworks.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).