DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1302] dpdk-pcapdump regression
Date: Thu, 19 Oct 2023 11:12:48 +0000	[thread overview]
Message-ID: <bug-1302-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

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

            Bug ID: 1302
           Summary: dpdk-pcapdump regression
           Product: DPDK
           Version: 23.03
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: nick.hedberg@gmail.com
  Target Milestone: ---

Created attachment 262
  --> https://bugs.dpdk.org/attachment.cgi?id=262&action=edit
testpmd output for the two commits

Commit 6026bfa breaks dumpcap on CX6 DX, the previous commit. 742be6a, didn't
show this issue. 
The error with this commit is: 
> ~/dpdk/build-6026bfa$ sudo ./app/dpdk-testpmd -c 0xf0 -n 4 -a 0000:03:00.0 --
> -i --port-topology=chained
...
> testpmd> start
> Packet forwarding already started
> testpmd> pdump_register_rx_callbacks(): rx callback for port=0 queue=0,
> already exists

and: 

>~/dpdk/build-6026bfa$ sudo ./app/dpdk-dumpcap -i 0  -c 6 -i 0 -w
>/tmp/sample.pcapng
File: /tmp/sample.pcapng
>pdump_prepare_client_request(): client request for pdump enable/disable failed
>EAL: Error - exiting with code: 1
>  Cause: Packet dump enable on 0:0000:03:00.0 failed Operation not permitted

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

[-- Attachment #2: Type: text/html, Size: 3529 bytes --]

                 reply	other threads:[~2023-10-19 11:12 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-1302-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).