From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1050] Burst packet receive from Mellanox gives "Segmentation fault" on CQE decompression
Date: Fri, 08 Jul 2022 08:56:36 +0000 [thread overview]
Message-ID: <bug-1050-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1050
Bug ID: 1050
Summary: Burst packet receive from Mellanox gives "Segmentation
fault" on CQE decompression
Product: DPDK
Version: unspecified
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: omer.yamac@ceng.metu.edu.tr
Target Milestone: ---
When I try to capture huge traffic, I got this segmentation fault. I have two
RX queue per ports. Totally I have two port and both have traffic. If the
traffic ratio is greater than 80Gbps (21Mpps), then I got the Segmentation
Fault.
I tried to check where is the error, I found that
In function `rxq_cq_decompress_v`, line 141 gives seg fault due to the null
value of elts. Also I shared a screen that includes Call Stack, elts values and
seg fault.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-07-08 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 8:56 bugzilla [this message]
2022-07-15 15:41 ` [Bug 1050] Burst packet receive from Mellanox gives "Segmentation fault" on CQE decompression bugzilla
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-1050-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.