From: Helmut Sim <simhelmut@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] eal_parse_coremask fails on SIGILL
Date: Tue, 24 Jun 2014 18:07:58 +0300 [thread overview]
Message-ID: <CAF8yGaFGs0AresKovc2TpRZxAzNsqN504DH4Eww6VqC58-itAA@mail.gmail.com> (raw)
In-Reply-To: <CAF8yGaHy-VMApi0HzZ+A8+soyCU-gSHu2s0tx=0Z9onwNJX6og@mail.gmail.com>
one more detail, i am using dpdk-1.6.0r1
On Tue, Jun 24, 2014 at 6:05 PM, Helmut Sim <simhelmut@gmail.com> wrote:
> Hi,
>
> I need some help to understand the following issue.
>
> I am building the DPDK with make install T=x86_64-default-linuxapp-gcc and
> it works well on my machine.
> However when testing it on my virtual machine (ubuntu 14.04 server guest n
> xen hv) it fails for SIGILL:
> here is the relevant gdb output for the helloworld example:
> [New LWP 4462]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `./build/helloworld -c 3 -n 4'.
> Program terminated with signal SIGILL, Illegal instruction.
> (gdb) bt
> #0 0x00000000004061d9 in eal_parse_coremask (coremask=0x7fff2bf9a9b1 "3")
> at
> /home/sim/work/prj/common/dpdk/package/lib/librte_eal/linuxapp/eal/eal.c:450
> #1 eal_parse_args (argv=0x7fff2bf99d68, argc=5) at
> /home/sim/work/prj/common/dpdk/package/lib/librte_eal/linuxapp/eal/eal.c:688
> #2 rte_eal_init (argc=5, argv=0x7fff2bf99d68) at
> /home/sim/work/prj/common/dpdk/package/lib/librte_eal/linuxapp/eal/eal.c:956
> #3 0x0000000000405436 in main ()
>
> i am building the dpdk and the examples on one machine and copy the
> x86_64-default-linuxapp-gcc and the helloworld/build directories to a
> second machine.
>
> the machine i am building the dpdk and the app on is:
> uname -a
> Linux sim 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014
> x86_64 x86_64 x86_64 GNU/Linux
>
> model name : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
> 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 ss ht tm pbe syscall nx
> pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
> xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
> ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
> movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida
> arat xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm
>
>
> the virtual machine i am executing the program on is:
> uname -a
> Linux vflow-target 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> from the cpuinfo:
> model name : Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc
> rep_good nopl pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt
> tsc_deadline_timer aes hypervisor lahf_lm
>
>
> Any idea why such an exception of SIGILL may occur?
>
>
> Thanks for your help.
>
>
next prev parent reply other threads:[~2014-06-24 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 15:05 Helmut Sim
2014-06-24 15:07 ` Helmut Sim [this message]
2014-06-24 17:32 ` Richardson, Bruce
2014-06-24 18:29 ` Helmut Sim
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=CAF8yGaFGs0AresKovc2TpRZxAzNsqN504DH4Eww6VqC58-itAA@mail.gmail.com \
--to=simhelmut@gmail.com \
--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).