[dpdk-users] Segfault while running on older CPU
contact at filipjaniszewski.com
Thu Feb 14 14:04:39 CET 2019
We've just encountered the same issue on a new server with a couple of
Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, stack trace the same:
Program received signal SIGILL, Illegal instruction.
0x0000000000557ce9 in rte_cpu_get_flag_enabled ()
Missing separate debuginfos, use: debuginfo-install
#0 0x0000000000557ce9 in rte_cpu_get_flag_enabled ()
#1 0x000000000046076e in rte_acl_init ()
#2 0x000000000085f56d in __libc_csu_init ()
#3 0x00007ffff6636365 in __libc_start_main () from /lib64/libc.so.6
#4 0x00000000004650de in _start ()
I'm building DPDK with x86_64-native-linuxapp-gcc, nothing else, plain
config from DPDK. I've attempted to recompile with CONFIG_RTE_EXEC_ENV
set to 'native' instead of 'linuxapp' but nothing changes.
Did anybody had a similar issue? Any suggestion?
Il 06/02/19 11:47, Filip Janiszewski ha scritto:
> Hi Everybody,
> We have one 'slightly' older machine (well, very old CPU.) in our Lab
> that seems to crash DPDK on every execution attempt, I was wondering if
> anybody encountered a similar issue and if there's a change in the DPDK
> config that might remedy the problem, this is the stack trace of the fault:
> #0 0x000000000057bd19 in rte_cpu_get_flag_enabled ()
> #1 0x000000000046067e in rte_acl_init ()
> #2 0x000000000088359d in __libc_csu_init ()
> #3 0x00007ffff6642cf5 in __libc_start_main () from /lib64/libc.so.6
> #4 0x0000000000464fee in _start ()
> The CPU on this machine is: "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
> (fam: 06, model: 3a, stepping: 09)" running with "3.10.0-862.el7.x86_64".
> Our builds are running fine on newest hardware, nevertheless the
> segfault seems a bit weird even for an unsupported CPU (some error
> prompt would be more friendly), any suggestion on what the problem might be?
+48 666 369 823
More information about the users