DPDK usage discussions
 help / color / mirror / Atom feed
From: Anthony Kanaan <anthony.kanaan1@gmail.com>
To: users@dpdk.org
Subject: illegal instruction (core dumped) problem
Date: Fri, 7 Apr 2023 10:02:16 +0200	[thread overview]
Message-ID: <CAKM=PUyXy9RF3Gr++p547A0gZJ2kTn99xVZSfjJdHGoD+03Cnw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2417 bytes --]

Hello,

I am having this problem when launching any DPDK application (including
helloworld):
illegal instruction (core dumped). I have tried to install several version
of DPDK: V22.11 V22.03 and 23.03 and non of them are working. I have
configure meson to build as a generic and native platform and non of them
are working.
You can find in the below the specs of the CPU:
Note that both the building PC and the target are the same PC.

Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   36 bits physical, 48 bits virtual
CPU(s):                          2
On-line CPU(s) list:             0,1
Thread(s) per core:              1
Core(s) per socket:              2
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           23
Model name:                      Intel(R) Core(TM)2 Duo CPU     E8400  @
3.00GHz
Stepping:                        10
CPU MHz:                         2911.124
BogoMIPS:                        5984.82
L1d cache:                       64 KiB
L1i cache:                       64 KiB
L2 cache:                        6 MiB
NUMA node0 CPU(s):               0,1
Vulnerability Itlb multihit:     KVM: Mitigation: VMX unsupported
Vulnerability L1tf:              Mitigation; PTE Inversion
Vulnerability Mds:               Vulnerable: Clear CPU buffers attempted,
no microcode; SMT disabled
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Mmio stale data:   Unknown: No mitigations
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and
__user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, STIBP disabled,
RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm
pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_
                                 good nopl cpuid aperfmperf pni dtes64
monitor ds_cpl smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti
dtherm

Thank you.

[-- Attachment #2: Type: text/html, Size: 3328 bytes --]

             reply	other threads:[~2023-04-12  6:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  8:02 Anthony Kanaan [this message]
2023-04-12  8:49 ` Dmitry Kozlyuk

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='CAKM=PUyXy9RF3Gr++p547A0gZJ2kTn99xVZSfjJdHGoD+03Cnw@mail.gmail.com' \
    --to=anthony.kanaan1@gmail.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).