DPDK patches and discussions
 help / color / mirror / Atom feed
From: Venkat Thummala <venkat.thummala.1978@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Running DPDK Binaries on a different Target
Date: Tue, 7 Apr 2015 17:28:59 +0530	[thread overview]
Message-ID: <CAF5bpL_9JVUfqMKf8ZA1V+RvDN3ZLEqkWY4_TaT2Ew3bZG13ew@mail.gmail.com> (raw)

Hi,

I have built a DPDK application [based on version 2.0] and run on the
native machine successfully.

I have tried running the binary on a different machine, but it resulted in
a CRASH with the following back trace.

Please find the CPU info of the machines from the attachment.

cpuinfo-1 - Native Machine
cpuinfo-2 - Non Native Machine

Could someone please help me in understanding the issue here and making it
work?

Regards
Venkat

Program terminated with signal SIGILL, Illegal instruction.
#0  0x00000000004209f2 in rte_cpu_get_flag_enabled (feature=2147483656,
feature@entry=RTE_CPUFLAG_EM64T)
    at
/home/vthummala/src/vwlc/dpdk/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_cpuflags.h:303
303        return (regs[feat->reg] >> feat->bit) & 1;
(gdb) bt
#0  0x00000000004209f2 in rte_cpu_get_flag_enabled (feature=2147483656,
feature@entry=RTE_CPUFLAG_EM64T)
    at
/home/vthummala/src/vwlc/dpdk/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_cpuflags.h:303
#1  0x0000000000420a1b in rte_hash_crc_set_alg (alg=6 '\006')
    at
/home/vthummala/src/vwlc/dpdk/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_hash_crc.h:429
#2  rte_hash_crc_init_alg () at
/home/vthummala/src/vwlc/dpdk/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_hash_crc.h:445
#3  0x000000000054968d in __libc_csu_init ()
#4  0x00007fc3ca474e55 in group_nodes_into_DFAstates
(dests_ch=0x940f507ab10ff0c8, dests_node=0x4a8b44de74c084c0,
state=0x4420528b48a8ebc9,
    dfa=<optimized out>) at regexec.c:3614
#5  build_trtable (dfa=0x840fc139c0014468, state=0x4420528b48a8ebc9) at
regexec.c:3354
#6  0x41d589495541f689 in ?? ()
#7  0x00251630258d4c54 in ?? ()
#8  0x002517302d8d4855 in ?? ()
#9  0xc148db31e5294c53 in ?? ()
#10 0x65e808ec834803fd in ?? ()
#11 0x1e74ed8548ffed48 in ?? ()
#12 0x0000000000841f0f in ?? ()

             reply	other threads:[~2015-04-07 11:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 11:58 Venkat Thummala [this message]
2015-04-07 12:00 ` Venkat Thummala
2015-04-07 14:35   ` Neil Horman
2015-04-08  8:33     ` Venkat Thummala
2015-04-08 11:47       ` Neil Horman
2015-04-09  9:07         ` Venkat Thummala
2015-04-09 11:37           ` Ananyev, Konstantin
2015-04-10  5:08             ` Venkat Thummala
2015-04-10  9:02               ` Venkat Thummala

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=CAF5bpL_9JVUfqMKf8ZA1V+RvDN3ZLEqkWY4_TaT2Ew3bZG13ew@mail.gmail.com \
    --to=venkat.thummala.1978@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).