DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bernd Schubert <bs_lists@aakef.fastmail.fm>
Cc: dev@dpdk.org
Subject: Re: SIGILL in rte_cpu_get_flag_enabled / RTE_CPUFLAG_RTM
Date: Mon, 25 Sep 2023 11:53:30 +0200	[thread overview]
Message-ID: <CAJFAV8wkaymjWfzbxgh0P=y3rCLX8XGUUu_h2rZqdrUaEYX9Nw@mail.gmail.com> (raw)
In-Reply-To: <089a8254-82e8-44a1-9641-4b6da6515dde@aakef.fastmail.fm>

On Fri, Sep 22, 2023 at 7:48 PM Bernd Schubert
<bs_lists@aakef.fastmail.fm> wrote:
>
> I'm trying to compile our tools on an older lab system and get
>
> Program received signal SIGILL, Illegal instruction.
> 0x00007ffff434c766 in rte_cpu_get_flag_enabled (feature=feature@entry=RTE_CPUFLAG_RTM) at ../lib/eal/x86/rte_cpuflags.c:173
> 173             return (regs[feat->reg] >> feat->bit) & 1;
> (gdb) bt
> #0  0x00007ffff434c766 in rte_cpu_get_flag_enabled (feature=feature@entry=RTE_CPUFLAG_RTM) at ../lib/eal/x86/rte_cpuflags.c:173
> #1  0x00007ffff3ffb572 in rte_rtm_init () at ../lib/eal/x86/rte_spinlock.c:14
> ##2  0x00007ffff7fc947e in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0x7fffffffe088, env=env@entry=0x7fffffffe098)
>      at ./elf/dl-init.c:70
> #3  0x00007ffff7fc9568 in call_init (env=0x7fffffffe098, argv=0x7fffffffe088, argc=1, l=<optimized out>) at ./elf/dl-init.c:33
> #4  _dl_init (main_map=0x7ffff7ffe2e0, argc=1, argv=0x7fffffffe088, env=0x7fffffffe098) at ./elf/dl-init.c:117
> #5  0x00007ffff7fe32ea in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
>
>
> This already has been reported here
> https://inbox.dpdk.org/users/C7FF2508-D633-404E-95AF-5F604D8E8E4B@intel.com/t/
> but I don't see a solution there. It just ends up asking for the line numbers.
> Well, the line is
>
>
>       __cpuid_count(feat->leaf, feat->subleaf,
>               regs[RTE_REG_EAX], regs[RTE_REG_EBX],
>               regs[RTE_REG_ECX], regs[RTE_REG_EDX]);
>
>      /* check if the feature is enabled */
>      return (regs[feat->reg] >> feat->bit) & 1; ====> line 173
>
>
> Maybe this should catch SIGILL?

SIGILL is a sign that some unsupported instruction (for your old cpu)
has been executed.
Did you try building dpdk with -Dplatform=generic meson option?


-- 
David Marchand


      parent reply	other threads:[~2023-09-25  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 17:48 Bernd Schubert
2023-09-22 18:02 ` Bernd Schubert
2023-09-25 17:11   ` Bernd Schubert
2023-09-25  9:53 ` David Marchand [this message]

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='CAJFAV8wkaymjWfzbxgh0P=y3rCLX8XGUUu_h2rZqdrUaEYX9Nw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bs_lists@aakef.fastmail.fm \
    --cc=dev@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).