DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: vikram T <vikramet@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Segmentation fault at rte_cpu_get_flag_enabled
Date: Mon, 20 Apr 2020 08:07:36 -0700	[thread overview]
Message-ID: <20200420080736.6934cee7@hermes.lan> (raw)
In-Reply-To: <CANxYRjy+CJ3Zsb-tZzMqC3RtOFWcGuO_r-GpnfU89+6BgHuTSQ@mail.gmail.com>

On Mon, 20 Apr 2020 12:39:02 +0530
vikram T <vikramet@gmail.com> wrote:

> Hi,
> I have been seeing the application crashes( DPDK v19.08) with segmentation
> fault as below:
> (gdb) bt
> #0  0x000000000054fda9 in rte_cpu_get_flag_enabled ()
> #1  0x00000000004f5d5e in rte_hash_crc_init_alg ()
> #2  0x000000000084cf7d in __libc_csu_init ()
> #3  0x00007ffff4df9425 in __libc_start_main () from /lib64/libc.so.6
> #4  0x00000000005048df in _start ()
> (gdb) q
> 
> Here the DPDK is built and linked on the machine different from the target
> machine.
> Hence used the flag - "CONFIG_RTE_MACHINE = default"  but no success.
> 
> Is there anything that needs to be followed to overcome this blocking issue?
> 
> Regards
> Vikram

You need to to set CONFIG_RTE_MACHINE to the minimum cpu type that your
product needs to run on. That value sets the compiler flags which determine
which extended CPU instructions will be used.

  reply	other threads:[~2020-04-20 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  7:09 vikram T
2020-04-20 15:07 ` Stephen Hemminger [this message]
2020-04-20 18:03   ` vikram T
2020-04-20 20:23     ` Stephen Hemminger

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=20200420080736.6934cee7@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=vikramet@gmail.com \
    /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).