From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1301] [dpdk-23.11] meson_tests/driver: core dumped occurred after link_bonding_autotest test
Date: Mon, 16 Oct 2023 06:53:03 +0000 [thread overview]
Message-ID: <bug-1301-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 4035 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1301
Bug ID: 1301
Summary: [dpdk-23.11] meson_tests/driver: core dumped occurred
after link_bonding_autotest test
Product: DPDK
Version: 23.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: songx.jiale@intel.com
Target Milestone: ---
[Environment]
DPDK version:
dpdk-23.11:77f913752a55c0262bfda99a1b69ca0bd804c6c7
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Ubuntu 22.04.3 LTS/5.15.0-82-generic
Compiler: gcc version 11.4.0
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
NIC hardware:
Intel Corporation Ethernet Controller E810-C for SFP [8086:1593] (rev 02)
NIC firmware:
driver: ice
version: 5.15.0-82-generic
firmware-version: 4.40 0x8001af8b 1.3444.0
[Test Setup]
1. compile dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=False -Dlibdir=lib --default-library=static
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc -j 72
2. blind port to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 05:00.0 08:00.0
3. start test
DPDK_TEST=link_bonding_autotest MALLOC_PERTURB_=94
/root/dpdk/x86_64-native-linuxapp-gcc/app/dpdk-test -c 0xff -a 0000:05:00.0 -a
0000:08:00.0
[Show the output from the previous commands.]
+ TestCase [62] : test_broadcast_verify_member_link_status_change_behaviour
succeeded
+ TestCase [63] : test_reconfigure_bonding_device succeeded
+ TestCase [64] : test_close_bonding_device succeeded
Invalid port_id=8
EAL: Test assert remove_members_and_stop_bonding_device line 658 failed: Failed
to stop bonding port 8
+ ------------------------------------------------------- +
+ Test Suite Summary : Link Bonding Unit Test Suite
+ ------------------------------------------------------- +
+ Tests Total : 65
+ Tests Skipped : 0
+ Tests Executed : 65
+ Tests Unsupported: 0
+ Tests Passed : 65
+ Tests Failed : 0
+ ------------------------------------------------------- +
Test OK
RTE>>Segmentation fault (core dumped)
[Expected Result]
no core dumped.
+ TestCase [62] : test_broadcast_verify_member_link_status_change_behaviour
succeeded
+ TestCase [63] : test_reconfigure_bonding_device succeeded
+ TestCase [64] : test_close_bonding_device succeeded
Invalid port_id=8
EAL: Test assert remove_members_and_stop_bonding_device line 658 failed: Failed
to stop bonding port 8
+ ------------------------------------------------------- +
+ Test Suite Summary : Link Bonding Unit Test Suite
+ ------------------------------------------------------- +
+ Tests Total : 65
+ Tests Skipped : 0
+ Tests Executed : 65
+ Tests Unsupported: 0
+ Tests Passed : 65
+ Tests Failed : 0
+ ------------------------------------------------------- +
Test OK
RTE>>
[Regression]
Is this issue a regression: (Y/N)Y
commit 36c46e738120c381cf663c96692454c5aa75e203
Author: David Marchand <david.marchand@redhat.com>
Date: Wed Sep 27 13:45:15 2023 +0200
ethdev: cleanup shared data with the last port
If no port is allocated and no port owner is still registered,
ethdev from a primary process may release the memzone used to store
port data.
This makes it possible for the DPDK memory allocator to release
associated resources back to the OS.
Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
lib/ethdev/ethdev_driver.c | 6 ++++++
lib/ethdev/ethdev_private.c | 21 ++++++++++++++++++++-
lib/ethdev/ethdev_private.h | 4 ++++
lib/ethdev/rte_ethdev.c | 3 +++
4 files changed, 33 insertions, 1 deletion
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 6126 bytes --]
reply other threads:[~2023-10-16 6:53 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-1301-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.