From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1366] mlx5 secondary testpmd process crash when calling rte_eth_stats_get
Date: Mon, 15 Jan 2024 14:24:53 +0000 [thread overview]
Message-ID: <bug-1366-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1366
Bug ID: 1366
Summary: mlx5 secondary testpmd process crash when calling
rte_eth_stats_get
Product: DPDK
Version: 22.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: eventdev
Assignee: dev@dpdk.org
Reporter: aidan@peralex.com
Target Milestone: ---
Created attachment 271
--> https://bugs.dpdk.org/attachment.cgi?id=271&action=edit
Secondary lldb process output
Linux:
AlmaLinux 9.3
Kernel:
5.14.0-362.8.1.el9_3.x86_64
Software version:
rdma-core-48.0-1.el9.x86_64
dpdk-v22.11(tested on git branch v23.11-rc4 as well)
Hardware:
Mellanox Technologies MT27800 Family [ConnectX-5]
Running two testpmd processes at the same time causes the secondary process to
crash with a segmentation fault from the libmlx5.so library. Two ports on a
Mellanox MT27800 card are configured to be used by both testpmd apps.
The two separate instances are launched:
1. dpdk-testpmd --proc-type=primary
2. dpdk-testpmd --proc-type=secondary
I am not sure if this is a rdma-core issue which contains the libmlx5.so
library where segmentation fault is thrown from. The primary dpdk process runs
without any issues and there are no segfaults. The rte_eth_stats_get function
only throws an error on the secondary process, not on the primary process.
Attached is the lldb output when running a debug build secondary process with
lldb.
Running dmesg also shows that there is a segfault:
dpdk-testpmd[67695]: segfault at b077f90 ip 00007f1ae42069e4 sp
00007ffcd49903b8 error 4 in libmlx5.so.1.24.48.0[7f1ae41b5000+5a000] likely on
CPU 0 (core 0, socket 0)
Code: 77 90 0f b6 d2 48 8d 05 7a a3 00 00 44 0f be 24 10 e9 7c ff ff ff e8 fb
f3 fa ff 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48>
8b 07 49 89 d2 4c 8d 0d 4f 88 01 00 48 8b 10 48 8b 92 98 02 00
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4140 bytes --]
reply other threads:[~2024-01-15 14:24 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-1366-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.