https://bugs.dpdk.org/show_bug.cgi?id=1024
Bug ID: 1024
Summary: [dpdk-22.07][meson test]
driver-tests/link_bonding_mode4_autotest bond
handshake failed
Product: DPDK
Version: unspecified
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: dpdk-22.07-rc0:eeab353b793109432538ba480a44de5dd3048032
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Ubuntu 22.04 LTS/ 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: i40e-5.15.0-27-generic/8.70 0x8000c40f 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.
meson test -C x86_64-native-linuxapp-gcc link_bonding_mode4_autotest -t 0.1
Show the output from the previous commands.
1/1 DPDK:driver-tests / link_bonding_mode4_autotest FAIL 22.68s
killed by signal 11 SIGSEGV
09:33:43 DPDK_TEST=link_bonding_mode4_autotest MALLOC_PERTURB_=42
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test
----------------------------------- output -----------------------------------
stdout:
RTE>>link_bonding_mode4_autotest^M
+ ------------------------------------------------------- +
+ Test Suite : Link Bonding mode 4 Unit Test Suite
+ ------------------------------------------------------- +
+ TestCase [ 0] : test_mode4_agg_mode_selection failed
+ TestCase [ 1] : test_mode4_lacp succeeded
+ TestCase [ 2] : test_mode4_rx succeeded
+ TestCase [ 3] : test_mode4_tx_burst succeeded
+ TestCase [ 4] : test_mode4_marker succeeded
+ TestCase [ 5] : test_mode4_expired succeeded
+ TestCase [ 6] : test_mode4_ext_ctrl succeeded
+ TestCase [ 7] : test_mode4_ext_lacp succeeded
+ ------------------------------------------------------- +
+ Test Suite Summary : Link Bonding mode 4 Unit Test Suite
+ ------------------------------------------------------- +
+ Tests Total : 8
+ Tests Skipped : 0
+ Tests Executed : 8
+ Tests Unsupported: 0
+ Tests Passed : 7
+ Tests Failed : 1
+ ------------------------------------------------------- +
Test Failed
RTE>>
stderr:
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
EAL: Using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(1)
EAL: Ignore mapping IO port bar(4)
EAL: Probe PCI driver: net_i40e (8086:158b) device: 0000:81:00.0 (socket 1)
APP: HPET is not enabled, using TSC as default timer
bond_ethdev_mode_set(1587) - Using mode 4, it is necessary to do TX burst and
RX burst at least every 100ms.
Device with port_id=1 already started
Device with port_id=2 already started
Device with port_id=3 already started
Device with port_id=4 already started
EAL: Test assert bond_handshake line 643 failed: Bond handshake failedEAL: Test
assert test_mode4_agg_mode_selection line 680 failed: Initial handshake failed
Device with port_id=1 already stopped
Expected Result
Test OK
Regression
Is this issue a regression: (Y/N) Y
First run it by using "meson test"
--
You are receiving this mail because:
You are the assignee for the bug.
