From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id F39FCA00E6 for ; Thu, 16 May 2019 12:40:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3D2C158EC; Thu, 16 May 2019 12:40:07 +0200 (CEST) Received: by dpdk.org (Postfix, from userid 33) id BF93D58EC; Thu, 16 May 2019 12:40:05 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Thu, 16 May 2019 10:40:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: doc X-Bugzilla-Version: 19.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: vipin.varghese@intel.com X-Bugzilla-Status: CONFIRMED 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 Subject: [dpdk-dev] [Bug 280] X710 PF Reset Issue with DPDK VF Driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D280 Bug ID: 280 Summary: X710 PF Reset Issue with DPDK VF Driver Product: DPDK Version: 19.05 Hardware: Other OS: Linux Status: CONFIRMED Severity: major Priority: Normal Component: doc Assignee: dev@dpdk.org Reporter: vipin.varghese@intel.com Target Milestone: --- LOGS: [93011.069202] i40e 0000:82:00.2: VF 11 successfully unset unicast promiscu= ous mode [95318.521782] i40e 0000:82:00.2: Malicious Driver Detection event 0x00 on = TX queue 141 PF number 0x02 VF number 0x4d [95318.521787] i40e 0000:82:00.2: TX driver issue detected, PF reset issued [95318.521801] i40e 0000:82:00.2: TX driver issue detected on VF 13 [95318.521803] i40e 0000:82:00.2: Too many MDD events on VF 13, disabled [95318.521804] i40e 0000:82:00.2: Use PF Control I/F to re-enable the VF [95895.281551] i40e 0000:82:00.2: read: 0x000e648c =3D 0x0007f3fd [96380.723377] i40e 0000:82:00.2: VF 13 successfully set multicast promiscu= ous mode [96380.723382] i40e 0000:82:00.2: VF 13 successfully unset unicast promiscu= ous mode [96380.787648] i40e 0000:82:00.3: VF 15 successfully set multicast promiscu= ous mode [96380.787650] i40e 0000:82:00.3: VF 15 successfully unset unicast promiscu= ous mode ROOT CAUSE: Sending incorrect packet size through TX queue causes the MDD failure. Solution: static uint16_t precheck_pkts(uint8_t port __rte_unused, uint16_t qidx __rte_unused, struct rte_mbuf **pkts, uint16_t nb_pkts, void *_ __rte_unu= sed) { if (unlikely(nb_pkts =3D=3D 0)) return nb_pkts; int i, j, k; struct rte_mbuf *ptr; struct rte_mbuf *replace[nb_pkts]; for (i =3D 0, j =3D 0, k =3D 0; i < nb_pkts; i++) { ptr =3D pkts[i]; if (ptr->pkt_len < 17) { replace[k++] =3D ptr; } else if (!(ptr->ol_flags & PKT_TX_TCP_SEG)) { if (ptr->nb_segs > 8 || ptr->pkt_len > 9728) replace[k++] =3D ptr; else pkts[j++] =3D ptr; } else if (ptr->nb_segs > 8 || ptr->tso_segsz < 256 || ptr->tso_segsz > 9674 || ptr->pkt_len > 262144) { replace[k++] =3D ptr; } else { pkts[j++] =3D ptr; } } for (i =3D 0; i < k; i++) rte_pktmbuf_free(replace[i]); //printf(" Port (%u) Queue (%u) nb_pkts - old (%u) new (%u) drop (%u)\n", port, qidx, nb_pkts, j, k); return j; } issue: neither `DPDK Release 19.05` nor `Known Issues and Limitations in Le= gacy Releases` --=20 You are receiving this mail because: You are the assignee for the bug.=