DPDK usage discussions
 help / color / mirror / Atom feed
From: "Xiaoping Yan (NSB)" <xiaoping.yan@nokia-sbell.com>
To: "users@dpdk.org" <users@dpdk.org>, Matan Azrad <matan@nvidia.com>,
	"dekelp@nvidia.com" <dekelp@nvidia.com>
Subject: RE: dpdk mlx5 driver crash in rxq_cq_decompress_v
Date: Mon, 3 Jul 2023 01:18:22 +0000	[thread overview]
Message-ID: <7902affaba614875bf33c6f88a43e1c6@nokia-sbell.com> (raw)
In-Reply-To: <5376a9878f1c4eaeadef8591ea0d26cd@nokia-sbell.com>

[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]

Hi,

@'dekelp@nvidia.com'<mailto:dekelp@nvidia.com>@'Matan Azrad'<mailto:matan@nvidia.com> Can you kindly suggest?
Thank you.

Br, Xiaoping

From: Xiaoping Yan (NSB)
Sent: 2023年6月27日 12:11
To: users@dpdk.org; 'Matan Azrad' <matan@nvidia.com>; 'dekelp@nvidia.com' <dekelp@nvidia.com>
Subject: dpdk mlx5 driver crash in rxq_cq_decompress_v

Hi,

dpdk version in use: 21.11.2

Mlx5 driver crashes in rxq_cq_decompress_v in traffic test after several minutes.
Stack trace:
(gdb) bt
#0  0x00007ffff58612bc in _mm_storeu_si128 (__B=..., __P=<optimized out>)
    at /usr/lib/gcc/x86_64-redhat-linux/12/include/emmintrin.h:739
#1  rxq_cq_decompress_v (rxq=rxq@entry=0x2abe5592f40, cq=cq@entry=0x2abe54fdb00, elts=elts@entry=0x2abe5594638)
    at ../dpdk-21.11/drivers/net/mlx5/mlx5_rxtx_vec_sse.h:142
#2  0x00007ffff5862c84 in rxq_burst_v (no_cq=<synthetic pointer>, err=0x7fffffffb848, pkts_n=4, pkts=<optimized out>,
    rxq=0x2abe5592f40) at ../dpdk-21.11/drivers/net/mlx5/mlx5_rxtx_vec.c:349
#3  mlx5_rx_burst_vec (dpdk_rxq=0x2abe5592f40, pkts=0x7fffffffbf80, pkts_n=32) at ../dpdk-21.11/drivers/net/mlx5/mlx5_rxtx_vec.c:393
#4  0x00005555556a0f41 in rte_eth_rx_burst (nb_pkts=32, rx_pkts=0x7fffffffbf80, queue_id=0, port_id=1)
    at /usr/include/rte_ethdev.h:5721
…
Attached is the error log “Unexpected CQE error syndrome…” and dump file

I found there was a similar bug here: https://bugs.dpdk.org/show_bug.cgi?id=334
But the fix (88c0733535d6 extend Rx completion with error handling) should already been included, as I’m using 21.11.2
Also below commit (fix to 88c0733535d6) is already included in my dpdk version.
commit 60b254e3923d007bcadbb8d410f95ad89a2f13fa
Author: Matan Azrad matan@nvidia.com<mailto:matan@nvidia.com>
Date:   Thu Aug 11 19:51:55 2022 +0300

    net/mlx5: fix Rx queue recovery mechanism

Any suggestion?
Thank you.

Br, Xiaoping


[-- Attachment #2: Type: text/html, Size: 8781 bytes --]

  reply	other threads:[~2023-07-03  1:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  4:11 Xiaoping Yan (NSB)
2023-07-03  1:18 ` Xiaoping Yan (NSB) [this message]
2023-07-03  3:35   ` Matan Azrad
2023-07-05  1:44     ` Alexander Kozyrev
2023-07-05  3:34       ` Xiaoping Yan (NSB)
2023-07-05  3:43         ` Xiaoping Yan (NSB)
     [not found]       ` <71b74157c94f4ff9a0bdaa633a086b95@nokia-sbell.com>
2023-07-11 20:47         ` Alexander Kozyrev
2023-07-12  2:23           ` Xiaoping Yan (NSB)
2023-07-27 12:42             ` Alexander Kozyrev
2023-10-13  3:25               ` Xiaoping Yan (NSB)

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=7902affaba614875bf33c6f88a43e1c6@nokia-sbell.com \
    --to=xiaoping.yan@nokia-sbell.com \
    --cc=dekelp@nvidia.com \
    --cc=matan@nvidia.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).