From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2EEFFA034C; Mon, 9 May 2022 18:03:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D542C410EE; Mon, 9 May 2022 18:03:02 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id C9499407FF for ; Mon, 9 May 2022 18:03:01 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 942CDA04FD; Mon, 9 May 2022 18:03:01 +0200 (CEST) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 20.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dmontgomery@juniper.net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org https://bugs.dpdk.org/show_bug.cgi?id=3D1007 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 DP= DK 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 0000:02:00.1 'Ethernet Connection X553 1GbE 15e4' drv=3Digb_uio unused=3Dixgbe,vfio-pci Network devices using kernel driver =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 0000:02:00.0 'Ethernet Connection X553 1GbE 15e4' if=3Denp2s0f0 drv=3Dixgbe unused=3Digb_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 co= de? --=20 You are receiving this mail because: You are the assignee for the bug.=