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 A236DA055F; Fri, 27 May 2022 11:24:42 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8EFD040E78; Fri, 27 May 2022 11:24:42 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id E811E40E5A for ; Fri, 27 May 2022 11:24:41 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id D29EFA0560; Fri, 27 May 2022 11:24:41 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1019] Cannot Rx after DPDK 22.03 version with iavf Date: Fri, 27 May 2022 09:24:41 +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: 22.03 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: happygmkim@gmail.com 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=3D1019 Bug ID: 1019 Summary: Cannot Rx after DPDK 22.03 version with iavf Product: DPDK Version: 22.03 Hardware: All OS: All Status: UNCONFIRMED Severity: major Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: happygmkim@gmail.com Target Milestone: --- Hi, Sometimes XL710 VF cannot Rx packets when startup with DPDK 22.03. It have been worked well before DPDK 22.03. 1. Reproduction : Send arp flooding packets in same subnet during DPDK driv= er initialization, it happens randomly. #!/bin/bash while [ true ] do sudo arping -i ethvf -w 0 -B -q done Rx stopped after "fault addr 0 [fault reason 05] PTE Write access is not se= t" message found. 2. Test environment 1) OS : Ubuntu 18.04 2) NIC : Intel XL710 SRIOV-VF 3) Used Kernel driver and F/W version Driver version: 2.1.14-k firmware-version: 7.10 0x800075e6 19.5.12 -> It happened other several other different drivers and F/W versions 3. Syslog May 23 03:55:32 xx[31168]: EAL: VFIO support initialized May 23 03:55:32 xx[31168]: EAL: Using IOMMU type 1 (Type 1) May 23 03:55:32 kernel: vfio-pci 0000:3b:02.3: enabling device (0000 -> 000= 2) May 23 03:55:33 xx[31168]: EAL: Probe PCI driver: net_iavf (8086:154c) devi= ce: 0000:3b:02.3 (socket 0) May 23 03:55:33 kernel: vfio-pci 0000:3b:02.4: enabling device (0000 -> 000= 2) May 23 03:55:33 xx[31168]: EAL: Probe PCI driver: net_iavf (8086:154c) devi= ce: 0000:3b:02.4 (socket 0) May 23 03:55:33 xx[31168]: TELEMETRY: No legacy callbacks, legacy socket not created May 23 03:55:33 xx[31168]: iavf_configure_queues(): RXDID[22] is not suppor= ted, request default RXDID[1] in Queue[0] May 23 03:55:34 kernel: i40e 0000:3b:00.0: Unprivileged VF 3 is attempting = to configure promiscuous mode May 23 03:55:34 kernel: i40e 0000:3b:00.0: Unprivileged VF 3 is attempting = to configure promiscuous mode May 23 03:55:34 xx[31168]: iavf_configure_queues(): RXDID[22] is not suppor= ted, request default RXDID[1] in Queue[0] May 23 03:55:34 kernel: DMAR: DRHD: handling fault status reg 302 May 23 03:55:34 kernel: DMAR: [DMA Write] Request device [3b:02.4] fault ad= dr 0 [fault reason 05] PTE Write access is not set May 23 03:55:34 kernel: i40e 0000:3b:00.0: Unprivileged VF 4 is attempting = to configure promiscuous mode May 23 03:55:34 kernel: DMAR: [DMA Write] Request device [3b:02.4] fault ad= dr 0 [fault reason 05] PTE Write access is not set May 23 03:55:34 kernel: DMAR: DRHD: handling fault status reg 500 4 --=20 You are receiving this mail because: You are the assignee for the bug.=