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: dmontgom...@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.
