https://bugs.dpdk.org/show_bug.cgi?id=1118
Bug ID: 1118
Summary: [dpdk-22.11.0rc1][meson test]
driver-tests/link_bonding_autotest test failed core
dumped
Product: DPDK
Version: 22.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: weiyuanx...@intel.com
Target Milestone: ---
[Environment]
DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
dpdk22.11.0rc1 5976328d91c3616b1ad841a9181e1da23a2980bf
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Ubuntu 22.04.1 LTS (Jammy Jellyfish)/5.15.0-27-generic
Compiler: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b.
NIC firmware:
driver: i40e
version: 5.15.0-27-generic
firmware-version: 9.00 0x8000cead 1.3179.0
[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.
1. Use the following command to build DPDK:
CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static
x86_64-native-linuxapp-gcc/
ninja -C x86_64-native-linuxapp-gcc/
2. Execute the following command in the dpdk directory.
MALLOC_PERTURB_=219 DPDK_TEST=link_bonding_autotest
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff
MALLOC_PERTURB_=219 DPDK_TEST=link_bonding_rssconf_autotest
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff
MALLOC_PERTURB_=219 DPDK_TEST=link_bonding_mode4_autotest
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff
Show the output from the previous commands.
root@dpdk-VF-dut247:~/dpdk# MALLOC_PERTURB_=219
DPDK_TEST=link_bonding_rssconf_autotest
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff
EAL: Detected CPU lcores: 72
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
APP: HPET is not enabled, using TSC as default timer
RTE>>link_bonding_rssconf_autotest
+ ------------------------------------------------------- +
+ Test Suite : RSS Dynamic Configuration for Bonding Unit Test Suite
+ ------------------------------------------------------- +
Floating point exception (core dumped)
root@dpdk-VF-dut247:~/dpdk# MALLOC_PERTURB_=219 DPDK_TEST=link_bonding_autotest
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff
EAL: Detected CPU lcores: 72
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
APP: HPET is not enabled, using TSC as default timer
RTE>>link_bonding_autotest
+ ------------------------------------------------------- +
+ Test Suite : Link Bonding Unit Test Suite
+ ------------------------------------------------------- +
Floating point exception (core dumped)
root@dpdk-VF-dut247:~/dpdk# MALLOC_PERTURB_=219
DPDK_TEST=link_bonding_mode4_autotest
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff
EAL: Detected CPU lcores: 72
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
APP: HPET is not enabled, using TSC as default timer
RTE>>link_bonding_mode4_autotest
+ ------------------------------------------------------- +
+ Test Suite : Link Bonding mode 4 Unit Test Suite
Floating point exception (core dumped)
[Expected Result]
Explain what is the expected result in text or as an example output:
Test ok.
[Regression]
Is this issue a regression: (Y/N) Y
d03c0e83cc0042dc35e37f984de15533b09e6ac9 is the first bad commit
commit d03c0e83cc0042dc35e37f984de15533b09e6ac9
Author: Ivan Malov <ivan.ma...@oktetlabs.ru>
Date: Sun Sep 11 15:19:01 2022 +0300
net/bonding: fix descriptor limit reporting
Commit 5be3b40fea60 ("net/bonding: fix values of descriptor limits")
breaks reporting of "nb_min" and "nb_align" values obtained from
back-end devices' descriptor limits. This means that work done
by eth_bond_slave_inherit_desc_lim_first() as well as
eth_bond_slave_inherit_desc_lim_next() gets dismissed.
Revert the offending commit and use proper workaround
for the test case mentioned in the said commit.
Meanwhile, the test case itself might be poorly constructed.
It tries to run a bond with no back-end devices attached,
but, according to [1] ("Requirements / Limitations"),
at least one back-end device must be attached.
[1] doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
Fixes: 5be3b40fea60 ("net/bonding: fix values of descriptor limits")
Cc: sta...@dpdk.org
Signed-off-by: Ivan Malov <ivan.ma...@oktetlabs.ru>
Reviewed-by: Andrew Rybchenko <andrew.rybche...@oktetlabs.ru>
Acked-by: Chas Williams <3ch...@gmail.com>
drivers/net/bonding/rte_eth_bond_pmd.c | 21 +++++++++++----------
1 file changed, 11 insertions, 10 deletions
--
You are receiving this mail because:
You are the assignee for the bug.
