Skip to contentSkip to conversation

mlx5: test/debug_autotest failed when enable CONFIG_RTE_LIBRTE_MLX5_PMD=y

dpdk-dev [email protected] 1 participant 1 message Feb 27, 2020

lore
Share & tools
lore
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=414

            Bug ID: 414
           Summary: mlx5: test/debug_autotest failed when enable
                    CONFIG_RTE_LIBRTE_MLX5_PMD=y
           Product: DPDK
           Version: 20.02
          Hardware: POWER
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: [email protected]
          Reporter: [email protected]

Target Milestone: ---

Compiled DPDK on powerpc with CONFIG_RTE_LIBRTE_MLX5_PMD=y the test/debug_autotest failed

#./ppc_64-power8-linuxapp-gcc/app/test -n 4 -c f RTE>>debug_autotest
....
1: [./ppc_64-power8-linuxapp-gcc/app/test(rte_dump_stack+0x38) [0xfabdbccaf08]] Child process terminated as expected - Test passed! test_exit_valChild process status: 139 and WIFEXITED = 0
Child process terminated with RC = 0
EAL: Error - exiting with code: 1
Cause: test_exit_valChild process status: 139 and WIFEXITED = 0
Child process terminated with RC = 0
Child process terminated with incorrect status (expected = 1)! Test Failed

Child process exited with SIGSEGV 11
dmesg reported

[ 1014.235043] test[121837]: unhandled signal 11 at 00000a1d55db62d0 nip

00000a1d06b3c4c0 lr 00000a1d06e9a8c8 code 1

when CONFIG_RTE_LIBRTE_MLX5_PMD=n
Test passed as expected
....
1: [./ppc_64-power8-linuxapp-gcc/app/test(rte_dump_stack+0x38) [0x7f845542528]] Child process terminated as expected - Test passed! test_exit_valChild process status: 0 and WIFEXITED = 1
EAL: Error - exiting with code: 1
Cause: test_exit_valChild process status: 256 and WIFEXITED = 1
EAL: Error - exiting with code: 2
Cause: test_exit_valChild process status: 512 and WIFEXITED = 1
EAL: Error - exiting with code: 255
Cause: test_exit_valChild process status: 65280 and WIFEXITED = 1
EAL: Error - exiting with code: -1
Cause: test_exit_valChild process status: 65280 and WIFEXITED = 1
test_exit Passed
Test OK
RTE>>quit

modified test_debug.c with some printf()
67 wait(&status);
68 printf("Child process status: %d and WIFEXITED = %d \n",
status,WIFEXITED(status));
69 #ifndef RTE_EAL_ALWAYS_PANIC_ON_ERROR
70 /*if(!WIFEXITED(status) || WEXITSTATUS(status) !=
(uint8_t)exit_val){ */
71 if(!WIFEXITED(status)) {
72 printf("Child process terminated with RC = %d\n",
WEXITSTATUS(status));
73 if ( WEXITSTATUS(status) != (uint8_t)exit_val) {
74 printf("Child process terminated with incorrect
status (expected = %d)!\n",
75 exit_val);
76 return -1;
77 }
78 }
79 #endif

I just found this in DPDK 20.02, will verify with other DPDK version.
OS: Linux ltc17u31 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:24 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux
System: power9

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.