From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1689] [24.11] dpdk_pdump and dumppcap does not work
Date: Thu, 03 Apr 2025 00:13:45 +0000 [thread overview]
Message-ID: <bug-1689-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 4514 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1689
Bug ID: 1689
Summary: [24.11] dpdk_pdump and dumppcap does not work
Product: DPDK
Version: 24.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: kanikamago@microsoft.com
Target Milestone: ---
Created attachment 308
--> https://bugs.dpdk.org/attachment.cgi?id=308&action=edit
Coredump
Primary application is run with following params: - -a $PCI
--vdev=net_vdev_netvsc0,iface=$IFNAME
Secondary application is run as ./dpdk-pdump -- --pdump
'port=1,queue=*,rx-dev=/home/dpdkworker/rx.pcap,tx-dev=/home/dpdkworker/tx.pcap'
Issue: Application cannot start with EAL: cannot initialize tailq:
VFIO_CDX_RESOURCE_LIST.
Find full Failure message in attachment (coredump_pdump_issue.png)
DPDK is statically compiled into application, and following libs are excluded
to tame the size of executable.
list(
REMOVE_ITEM
DPDK_STATIC_LDFLAGS
-l:librte_baseband_acc100.a -l:librte_baseband_fpga_5gnr_fec.a
-l:librte_baseband_fpga_lte_fec.a -l:librte_baseband_null.a
-l:librte_baseband_turbo_sw.a
-l:librte_bus_dpaa.a -l:librte_bus_fslmc.a -l:librte_bus_ifpga.a
-l:librte_common_cpt.a
-l:librte_common_dpaax.a -l:librte_common_iavf.a -l:librte_common_octeontx.a
-l:librte_common_octeontx2.a
-l:librte_compress_octeontx.a -l:librte_crypto_bcmfs.a
-l:librte_crypto_caam_jr.a
-l:librte_crypto_ccp.a -l:librte_crypto_dpaa_sec.a -l:librte_crypto_dpaa2_sec.a
-l:librte_crypto_nitrox.a
-l:librte_crypto_octeontx.a -l:librte_crypto_octeontx2.a -l:librte_event_dpaa.a
-l:librte_event_dpaa2.a
-l:librte_event_dsw.a -l:librte_event_octeontx.a -l:librte_event_octeontx2.a
-l:librte_mempool_dpaa.a
-l:librte_mempool_dpaa2.a -l:librte_mempool_octeontx.a
-l:librte_mempool_octeontx2.a -l:librte_net_ark.a
-l:librte_net_atlantic.a -l:librte_net_avp.a -l:librte_net_axgbe.a
-l:librte_net_bnx2x.a -l:librte_net_bnxt.a
-l:librte_net_bond.a -l:librte_net_cxgbe.a -l:librte_net_dpaa.a
-l:librte_net_dpaa2.a -l:librte_net_ena.a
-l:librte_net_enetc.a -l:librte_net_enic.a -l:librte_net_fm10k.a
-l:librte_net_hinic.a -l:librte_net_hns3.a -l:librte_net_i40e.a
-l:librte_net_iavf.a -l:librte_net_ice.a
-l:librte_net_igc.a -l:librte_net_liquidio.a -l:librte_net_memif.a
-l:librte_net_nfp.a
-l:librte_net_octeontx.a -l:librte_net_octeontx2.a -l:librte_net_pfe.a
-l:librte_net_qede.a
-l:librte_net_sfc.a -l:librte_net_thunderx.a -l:librte_net_txgbe.a
-l:librte_raw_dpaa2_cmdif.a
-l:librte_raw_dpaa2_qdma.a -l:librte_raw_octeontx2_dma.a
-l:librte_raw_octeontx2_ep.a
-l:librte_net_ntnic.a -l:librte_regex_octeontx2.a -l:librte_raw_cnxk_bphy.a
-l:librte_raw_cnxk_gpio.a -l:librte_raw_cnxk_rvu_lf.a
-l:librte_raw_cnxk_rvu_pf.a -l:librte_regex_cn9k.a -l:librte_net_zxdh.a
-l:librte_net_vmxnet3.a
-l:librte_net_octeon_ep.a -l:librte_net_r8169.a -l:librte_net_cpfl.a
-l:librte_net_cxgbe.a -l:librte_net_dpaa.a
-l:librte_net_dpaa2.a -l:librte_net_enetfec.a -l:librte_net_gve.a
-l:librte_net_idpf.a -l:librte_net_ionic.a
-l:librte_dma_dpaa.a -l:librte_dma_dpaa2.a -l:librte_event_cnxk.a
-l:librte_baseband_la12xx.a
-l:librte_common_cnxk.a -l:librte_dma_cnxk.a -l:librte_common_idpf.a
-l:librte_common_ionic.a -l:librte_mempool_cnxk.a
-l:librte_crypto_cnxk.a -l:librte_crypto_ionic.a -l:librte_net_cnxk.a
-l:librte_ml_cnxk.a -l:librte_net_softnic.a -l:librte_dma_odm.a
-l:librte_event_dlb2.a -l:librte_event_opdl.a -l:librte_event_skeleton.a
-l:librte_event_octeontx.a -l:librte_dma_skeleton.a -l:librte_raw_skeleton.a
-l:librte_dma_hisilicon.a -l:librte_dma_idxd.a -l:librte_dma_ioat.a
-l:librte_compress_nitrox.a -l:librte_compress_zlib.a
-l:librte_common_qat.a -l:librte_common_sfc_efx.a -l:librte_common_nfp.a
-l:librte_baseband_acc.a -l:librte_vdpa_nfp.a
-l:librte_vdpa_ifc.a -l:librte_vdpa_sfc.a -l:librte_net_e1000.a
-l:librte_net_ixgbe.a
-l:librte_bus_cdx.a -l:librte_bus_uacce.a -l:librte_common_nitrox.a
-l:librte_raw_ntb.a
To debug we recompiled application with no lib exclusions, and reran, the pdump
and dumppcap applications could start and capture packet, but when terminated
they caused primary application to terminate and exited with output as in
attached image pdump_issue_no_exclusions.png
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 6496 bytes --]
reply other threads:[~2025-04-03 0:13 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-1689-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 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).