DPDK usage discussions
 help / color / mirror / Atom feed
From: Filip Janiszewski <contact@filipjaniszewski.com>
To: users@dpdk.org
Subject: [dpdk-users] Segfault while running on older CPU
Date: Wed, 6 Feb 2019 11:47:08 +0100	[thread overview]
Message-ID: <61d2793d-ca13-fdb3-e54f-4db40d95e9e0@filipjaniszewski.com> (raw)

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?

Thanks

-- 
BR, Filip
+48 666 369 823

             reply	other threads:[~2019-02-06 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 10:47 Filip Janiszewski [this message]
2019-02-14 13:04 ` Filip Janiszewski
2019-02-14 13:34   ` Wiles, Keith
2019-02-14 14:15     ` Filip Janiszewski
2019-02-14 14:46       ` Van Haaren, Harry
2019-02-15  5:45         ` Filip Janiszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61d2793d-ca13-fdb3-e54f-4db40d95e9e0@filipjaniszewski.com \
    --to=contact@filipjaniszewski.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).