DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 6] dpdk-pdump leads to ovs-vswitchd crash
Date: Thu, 04 Jan 2018 06:19:35 +0000	[thread overview]
Message-ID: <bug-6-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=6

            Bug ID: 6
           Summary: dpdk-pdump leads to ovs-vswitchd crash
           Product: DPDK
           Version: 17.11
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: critical
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: wangzhike@jd.com
  Target Milestone: ---

I am using dpdk17.11 and latest openvswitch (pre-2.9). When I tries to dump the
packets on dpdk port, the ovs-vswitchd crash.

The command is as follows:
/usr/bin/dpdk-pdump -d librte_pmd_pcap.so -- --pdump
port=0,queue=*,rx-dev=/tmp/pkts1.pcap,tx-dev=/tmp/pkts1.pcap
--server-socket-path=/var/run/openvswitch

It can be reproduced 100%. it was broken even on 17.05. 

It works on dpdk 16.11.

Br,
Wang Zhike

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

                 reply	other threads:[~2018-01-04  6:19 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-6-3@http.dpdk.org/tracker/ \
    --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).