Re: [dpdk-dev] Running DPDK Binaries on a different Target

[Venkat Thummala <venkat.thummala.1978@gmail.com>]

Attaching the CPU Info.

On 7 April 2015 at 17:28, Venkat Thummala <venkat.thummala.1978@gmail.com>
wrote:

> 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 ?? ()
>