From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 17653A00C2; Mon, 31 Oct 2022 09:52:27 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E41DE40151; Mon, 31 Oct 2022 09:52:26 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 50B93400D5 for ; Mon, 31 Oct 2022 09:52:25 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 155D9A034C; Mon, 31 Oct 2022 09:52:24 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1118] [dpdk-22.11.0rc1][meson test] driver-tests/link_bonding_autotest test failed core dumped Date: Mon, 31 Oct 2022 08:52:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: meson X-Bugzilla-Version: 22.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weiyuanx.li@intel.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org https://bugs.dpdk.org/show_bug.cgi?id=3D1118 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.li@intel.com Target Milestone: --- [Environment] DPDK version: Use make showversion or for a non-released version: git remot= e -v && git show-ref --heads dpdk22.11.0rc1 5976328d91c3616b1ad841a9181e1da23a2980bf Other software versions: name/version for QEMU, OVS, etc. Repeat as require= d. 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:=20 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:=20 CC=3Dgcc meson -Denable_kmods=3DTrue -Dlibdir=3Dlib --default-library=3Dsta= tic x86_64-native-linuxapp-gcc/=20 ninja -C x86_64-native-linuxapp-gcc/=20 2. Execute the following command in the dpdk directory.=20=20=20 MALLOC_PERTURB_=3D219 DPDK_TEST=3Dlink_bonding_autotest /root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff MALLOC_PERTURB_=3D219 DPDK_TEST=3Dlink_bonding_rssconf_autotest /root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff MALLOC_PERTURB_=3D219 DPDK_TEST=3Dlink_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_=3D219 DPDK_TEST=3Dlink_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_=3D219 DPDK_TEST=3Dlink_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_=3D219 DPDK_TEST=3Dlink_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 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: stable@dpdk.org Signed-off-by: Ivan Malov Reviewed-by: Andrew Rybchenko Acked-by: Chas Williams <3chas3@gmail.com> drivers/net/bonding/rte_eth_bond_pmd.c | 21 +++++++++++---------- 1 file changed, 11 insertions, 10 deletions --=20 You are receiving this mail because: You are the assignee for the bug.=