From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 571] [dpdk-20.11]packet_capture: can't start pdump.
Date: Mon, 09 Nov 2020 06:56:35 +0000 [thread overview]
Message-ID: <bug-571-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=571
Bug ID: 571
Summary: [dpdk-20.11]packet_capture: can't start pdump.
Product: DPDK
Version: 20.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: junx.w.zhou@intel.com
Target Milestone: ---
DPDK version:
20.11-rc3 60af9bd63dd46ebd709371e88b4096fd2bc048cf
OS: CentOS Linux release 8.2.2004
Compiler: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
NIC hardware: Fortville_25g(Ethernet Controller XXV710 for 25GbE SFP28 158b)
NIC firmware:
driver: i40e
version: 2.13.10
firmware-version: 8.00 0x80008c1a 1.2766.0
Test Setup
Steps to reproduce
List the steps to reproduce the issue.
1.usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:05:00.0 0000:05:00.1
2.x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1,2 -n 4 -w 0000:05:00.0 -w
0000:05:00.1 --file-prefix=test -- -i --port-topology=chained
3.set fwd io
4.start
5.new session:x86_64-native-linuxapp-gcc/app/dpdk-pdump -v --file-prefix=test
-- --pdump
'port=0,queue=*,tx-dev=/tmp/pdumpLog/pdump-tx.pcap,rx-dev=/tmp/pdumpLog/pdump-rx.pcap'
Show the output from the previous commands.
EAL: Detected 88 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: RTE Version: 'DPDK 20.11.0-rc1'
EAL: Multi-process socket /var/run/dpdk/test/mp_socket_470986_13014e4b81e444
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_i40e (8086:158b) device: 0000:05:00.0 (socket 0)
EAL: Probe PCI driver: net_i40e (8086:158b) device: 0000:05:00.1 (socket 0)
RING: Cannot reserve memory
EAL: Error - exiting with code: 1
Cause: File exists:create_mp_ring_vdev:673
Expected Result
Explain what is the expected result in text or as an example output:
no error log
Regression
Is this issue a regression: (Y)
Version the regression was introduced:
commit d23d73d088c1bdab8385fa64cd397ccedc725472
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Thu Oct 29 08:17:35 2020 +0100
net/pcap: switch Rx timestamp to dynamic mbuf field
The mbuf timestamp is moved to a dynamic field
in order to allow removal of the deprecated static field.
The related mbuf flag is also replaced.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: David Marchand <david.marchand@redhat.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-11-09 6:56 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=bug-571-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.