DPDK usage discussions
 help / color / mirror / Atom feed
From: Ken Andrews <ken.andrews@calnexsol.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Mellanox - Unexpected CEQ error, rx stops receiving packets
Date: Fri, 28 Jun 2024 09:22:39 +0000	[thread overview]
Message-ID: <CWLP265MB649951D023BC6FF080A92A14EED02@CWLP265MB6499.GBRP265.PROD.OUTLOOK.COM> (raw)

Hi,

I'm seeing an issue previously mentioned on this list in 2022, where my Mellanox NIC is logging an Unexpected CEQ error syndrome. Once this condition is hit, the 
rxq->err_state var in the mlx5 PMD is never cleared, and the rx just loops around never receiving any further packets. 

It's not clear what's causing the initial CEQ error, as it can take upwards of an hour to occur.

The full log entry is:

Unexpected CQE error syndrome 0x04 CQN = 256 SQN = 4679 wqe_counter = 2149 wq_ci = 3294 cq_ci = 42609
MLX5 Error CQ: at [0x292d26000], len=16384

The NIC is:  NVIDIA ConnectX-7 HHHL Adapter card, 400GbE / NDR IB (default mode), Single-port OSFP, PCIe 5.0 x16, Crypto Enabled, Secure Boot Enabled
Part number: MCX75310AAC-NEA_Ax
Firmware: 28.36.1010
OFED Version: 24.04-0.6.6.0
DPDK Version: 23.11.0

This issue was previously mentioned in this post: https://mails.dpdk.org/archives/users/2022-October/006779.html

Can anyone please help shed some light on this?

Thanks,
Ken AndrewsKen Andrews R&D Departmentt: +44 1506 671416e: ken.andrews@calnexsol.comw: calnexsol.comNew Product

The SNE-X is a total solution to the problem of real-world Ethernet testing. It combines comprehensive and efficient network emulation for 5G, Data Center, and Cloud applications. Click for more information.

Calnex Solutions
Oracle Campus
Linlithgow
EH49 7LR
United KingdomCalnex Solutions plc is registered in Scotland. Registration number: SC299625. Registered office: Oracle Campus, Linlithgow, Scotland, EH49 7LR, United Kingdom.

                 reply	other threads:[~2024-06-28  9:23 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=CWLP265MB649951D023BC6FF080A92A14EED02@CWLP265MB6499.GBRP265.PROD.OUTLOOK.COM \
    --to=ken.andrews@calnexsol.com \
    --cc=users@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).