From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1688] [24.11] random application crash in failsafe_rx_burst_fast
Date: Wed, 02 Apr 2025 23:55:34 +0000 [thread overview]
Message-ID: <bug-1688-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1688
Bug ID: 1688
Summary: [24.11] random application crash in
failsafe_rx_burst_fast
Product: DPDK
Version: 24.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: kanikamago@microsoft.com
Target Milestone: ---
Created attachment 307
--> https://bugs.dpdk.org/attachment.cgi?id=307&action=edit
Coredump of application crash
we recently upgraded our packet processing application from 20.11 to 24.11 LTS
dpdk version. The change when rolled to canary is causing nodes to crash
randomly. The crash is not recurring i.e. when node is recovered the
application starts and runs.
Host OS - Windows
Guest OS - Linux (Mariner), application running here
Linkage - DPDK statically compiled into app
Crash callstack - Attached as Image
NIC - Mellanox ConnectX-3-pro
Application params - -a $PCI --vdev=net_vdev_netvsc0,iface=$IFNAME
Secondary application - None
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3256 bytes --]
reply other threads:[~2025-04-02 23:55 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-1688-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).