DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 2075] pdump fails on hairpin queue
Date: Tue, 27 Oct 2026 13:55:05 +0000	[thread overview]
Message-ID: <bug-2075-3@https.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=2075

            Bug ID: 2075
           Summary: pdump fails on hairpin queue
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

Message from Haan on Slack reported issue with dpdk-dumpcap with hairpin queue

Hello all,

I found a problem with dpdk-dumpcap that makes it fail to capture, it happens
if a DPDK program has a port that has a haripin queue, the first run fails with
Unknown error -22 , every later run on the same port fails with File exists.

Steps to reproduce:

1. Start testpmd with one hairpin queue per port:

   dpdk-testpmd -l 0-1 -a <PCI_ADDR> -- -i --rxq=1 --txq=1 --hairpinq=1
   testpmd> start

2. In another shell, run dumpcap:

   dpdk-dumpcap -i 0 -w /tmp/zzz.pcap

Result:

File: zzz.pcap
PDUMP: pdump_prepare_client_request(): client request for pdump enable/disable
failed
EAL: Error - exiting with code: 1
Packet dump enable on 0:0000:01:00.0 failed Unknown error -22

3. Run the same dumpcap command again:

Result:

File: zzz.pcap
PDUMP: pdump_prepare_client_request(): client request for pdump enable/disable
failed
EAL: Error - exiting with code: 1
Packet dump enable on 0:0000:01:00.0 failed File exists

Any idea how can I use it to capture even if there's a haripin queue?

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2026-10-27 13:55 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-2075-3@https.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