From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1698] rte_eth_rx_burst causes segmentation fault when encountered in a Secondary process
Date: Thu, 24 Apr 2025 09:46:03 +0000 [thread overview]
Message-ID: <bug-1698-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1698
Bug ID: 1698
Summary: rte_eth_rx_burst causes segmentation fault when
encountered in a Secondary process
Product: DPDK
Version: 23.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: reuben.koshy@vvdntech.in
Target Milestone: ---
Created attachment 311
--> https://bugs.dpdk.org/attachment.cgi?id=311&action=edit
This is the screenshot of the log that appears when the secondary process
tries to execute tx_burst
I took a copy of the simple_mp main program from multi_process within the DPDK
examples and modified it by adding bonding and allowing it to send dummy
packets.
Two bonds are created, both are under the Active backup mode. This is done by
the primary process.
Once the bonds are created, configured and started, the transmisssion of dummy
packets starts. When tx_burst is run for the primary process, the transmission
of packets occur without any issue.
However, when the tx_burst is encountered during the Secondary process with the
primary process running in another terminal, a segmentation error occurs.
DPDK Version : 23.11
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3633 bytes --]
reply other threads:[~2025-04-24 9:46 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-1698-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).