From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1238] net/mlx5: RxQ failure with vectorized MPRQ
Date: Fri, 26 May 2023 00:31:02 +0000 [thread overview]
Message-ID: <bug-1238-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1238
Bug ID: 1238
Summary: net/mlx5: RxQ failure with vectorized MPRQ
Product: DPDK
Version: 23.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: dmitry.kozliuk@gmail.com
Target Milestone: ---
CPU: Intel(R) Xeon(R) Gold 6238R CPU @ 2.20GHz
NIC: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
OFED: MLNX_OFED_LINUX-23.04-0.5.3.3
FW: 16.35.2000
Kernel: 5.10.0-21-amd64
Commit 633684e0 "net/mlx5: fix error CQE dumping for vectorized Rx" presumably
introduced a regression: Rx queues eventually stop with "CQ error on CQN 0x57d,
syndrome 0x1" in dmesg. There is unfortunately no repro with testpmd yet. The
error happens under certain CPU load from an app and with a different delay for
each RxQ, which suggests that this may be a concurrency issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3009 bytes --]
reply other threads:[~2023-05-26 0:31 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-1238-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).