Re: [dpdk-users] Segfault while running on older CPU

2019-02-14 Thread Filip Janiszewski
Il 14/02/19 15:46, Van Haaren, Harry ha scritto: >> -Original Message- >> From: users [mailto:users-boun...@dpdk.org] On Behalf Of Filip Janiszewski >> Sent: Thursday, February 14, 2019 2:15 PM >> To: Wiles, Keith >> Cc: users@dpdk.org >> Subj

Re: [dpdk-users] Segfault while running on older CPU

2019-02-14 Thread Van Haaren, Harry
> -Original Message- > From: users [mailto:users-boun...@dpdk.org] On Behalf Of Filip Janiszewski > Sent: Thursday, February 14, 2019 2:15 PM > To: Wiles, Keith > Cc: users@dpdk.org > Subject: Re: [dpdk-users] Segfault while running on older CPU > > Hi, >

Re: [dpdk-users] Segfault while running on older CPU

2019-02-14 Thread Filip Janiszewski
Hi, I prepared a simple test application with only a call to rte_eal_init and it crashes, DPDK version is 18.05 and apparently the problem is with the BMI2 instruction set, the faulty line is: . │0x57fec9 shrx %eax,%edx,%eax . I'm attempting to disable those instructions by setting march

Re: [dpdk-users] Segfault while running on older CPU

2019-02-14 Thread Wiles, Keith
> On Feb 14, 2019, at 7:04 AM, Filip Janiszewski > wrote: > > Hi All, > > 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: > What version of DPDK? > . > Program received signal SIGILL, Illegal

Re: [dpdk-users] Segfault while running on older CPU

2019-02-14 Thread Filip Janiszewski
Hi All, 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. 0x00557ce9 in rte_cpu_get_flag_enabled () Missing separate debuginfos, use:

[dpdk-users] Segfault while running on older CPU

2019-02-06 Thread Filip Janiszewski
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