From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 280] X710 PF Reset Issue with DPDK VF Driver
Date: Thu, 16 May 2019 10:40:05 +0000 [thread overview]
Message-ID: <bug-280-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=280
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 promiscuous
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 = 0x0007f3fd
[96380.723377] i40e 0000:82:00.2: VF 13 successfully set multicast promiscuous
mode
[96380.723382] i40e 0000:82:00.2: VF 13 successfully unset unicast promiscuous
mode
[96380.787648] i40e 0000:82:00.3: VF 15 successfully set multicast promiscuous
mode
[96380.787650] i40e 0000:82:00.3: VF 15 successfully unset unicast promiscuous
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_unused)
{
if (unlikely(nb_pkts == 0))
return nb_pkts;
int i, j, k;
struct rte_mbuf *ptr;
struct rte_mbuf *replace[nb_pkts];
for (i = 0, j = 0, k = 0; i < nb_pkts; i++)
{
ptr = pkts[i];
if (ptr->pkt_len < 17) {
replace[k++] = ptr;
} else if (!(ptr->ol_flags & PKT_TX_TCP_SEG)) {
if (ptr->nb_segs > 8 ||
ptr->pkt_len > 9728)
replace[k++] = ptr;
else
pkts[j++] = ptr;
} else if (ptr->nb_segs > 8 ||
ptr->tso_segsz < 256 ||
ptr->tso_segsz > 9674 ||
ptr->pkt_len > 262144) {
replace[k++] = ptr;
} else {
pkts[j++] = ptr;
}
}
for (i = 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 Legacy
Releases`
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-05-16 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-280-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).