DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1007] ixgbe-bound x553 sibling interface broken after app crash
Date: Mon, 09 May 2022 16:03:01 +0000	[thread overview]
Message-ID: <bug-1007-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1007
           Summary: ixgbe-bound x553 sibling interface broken after app
                    crash
           Product: DPDK
           Version: 20.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: dmontgomery@juniper.net
  Target Milestone: ---

We have two interfaces on one chipset, one bound to igb_uio for use in a DPDK
application, the sibling still owned by linux.  After an application crash, the
device we were *not* using stops receiving packets.

dpdk-devbind.py snippet:

[root@sn9120210013 ~]# dpdk-devbind.py --status

Network devices using DPDK-compatible driver
============================================
0000:02:00.1 'Ethernet Connection X553 1GbE 15e4' drv=igb_uio
unused=ixgbe,vfio-pci

Network devices using kernel driver
===================================
0000:02:00.0 'Ethernet Connection X553 1GbE 15e4' if=enp2s0f0 drv=ixgbe
unused=igb_uio,vfio-pci

Using ethtool on enp2s0f0, we see these counters:

     rx_packets: 1389712
     rx_bytes: 478998162
     rx_pkts_nic: 1398666
     rx_bytes_nic: 485323772

rx_packets and rx_bytes halt, but rx_pkts_nic and rx_bytes_nic continue
incrementing.

Is there any chance there is bleedover to sibling devices inside the PMD code?

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

             reply	other threads:[~2022-05-09 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 16:03 bugzilla [this message]
2023-11-09  5:53 ` bugzilla

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-1007-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).