DPDK patches and discussions
 help / color / mirror / Atom feed
From: Clarylin L <clearasu@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [dpdk-pdump] Problem with dpdk-pdump
Date: Mon, 30 Jan 2017 14:52:08 -0800	[thread overview]
Message-ID: <CAKj5MjtXB8J1qe-gaT==8b-8TP1D=+ArMmdDYu0P_WXHsTkoHg@mail.gmail.com> (raw)

Hi all,

I just started to use dpdk-pdump and got some problem with it. Appreciate
your help!

By following the document, I got testpmd running with pdump framework
initialized and tried to start dpdk-pdump as a secondary process. However,
I failed to start dpdk-pdump.

My testpmd was running like:

testpmd -w 0000:00:05.0 -w 0000:00:06.0 -n 2 -c 0xf --socket-mem 1024 0
--proc-type primary --syslog local4


Then I started dpdk-pdump like


dpdk-pdump -w 0000:00:05.0 -w 0000:00:06.0 -- --pdump
'port=0,queue=*,rx-dev=/tmp/rx.pcap’


but got error messages as shown below. I double check the PCI device
0000:00:05.0 and it was bounded to dpdk driver (I specified whitelist
because I have more than two ports in my system and only two of them were
given to dpdk)


EAL: Detected 8 lcore(s)

Mon Jan 30 17:23:35 2017EAL: WARNING: cpu flags constant_tsc=yes
nonstop_tsc=no -> using unreliable clock cycles !

Mon Jan 30 17:23:35 2017PMD: bnxt_rte_pmd_init() called for (null)

Mon Jan 30 17:23:35 2017EAL: PCI device 0000:00:05.0 on NUMA socket -1

Mon Jan 30 17:23:35 2017EAL:   probe driver: 1137:43 rte_enic_pmd

Mon Jan 30 17:23:35 2017PMD: rte_enic_pmd: vNIC BAR0 res hdr not mem-mapped

Mon Jan 30 17:23:35 2017PMD: rte_enic_pmd: vNIC registration failed,
aborting

Mon Jan 30 17:23:35 2017EAL: Error - exiting with code: 1

  Cause: Mon Jan 30 17:23:35 2017Requested device 0000:00:05.0 cannot be
used

                 reply	other threads:[~2017-01-30 22:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAKj5MjtXB8J1qe-gaT==8b-8TP1D=+ArMmdDYu0P_WXHsTkoHg@mail.gmail.com' \
    --to=clearasu@gmail.com \
    --cc=dev@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).