From: Surya Nimmagadda <nscsekhar@juniper.net>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Illegal instruction at rte_malloc_socket
Date: Tue, 24 Dec 2013 01:05:01 +0000 [thread overview]
Message-ID: <4f69b88f0cab464faee28a2f27988852@CO1PR05MB284.namprd05.prod.outlook.com> (raw)
Hi,
When I try to run the sample applications like l2fwd or exception_path, they get aborted at rte_malloc_socket.
Can someone please take a look and let me know what I am missing?
Here is a back trace when I run in gdb:
EAL: Master core 0 is ready (tid=f7df6800)
[New Thread 0xb67fab40 (LWP 4480)]
EAL: Core 1 is ready (tid=b67fab40)
[New Thread 0xb5ff9b40 (LWP 4481)]
EAL: Core 2 is ready (tid=b5ff9b40)
[New Thread 0xb57f8b40 (LWP 4482)]
EAL: Core 3 is ready (tid=b57f8b40)
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: probe driver: 8086:100e rte_em_pmd
Program received signal SIGILL, Illegal instruction.
0x080c3084 in rte_malloc_socket ()
(gdb)
Here are my setup details:
Environment : Ubuntu VM
$echo $RTE_TARGET
i686-default-linuxapp-gcc
Network devices using IGB_UIO driver
====================================
0000:00:03.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
0000:00:04.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
Network devices using kernel driver
===================================
0000:00:05.0 '82540EM Gigabit Ethernet Controller' if=eth2 drv=e1000 unused=igb_uio
0000:00:06.0 '82540EM Gigabit Ethernet Controller' if=eth3 drv=e1000 unused=igb_uio *Active*
next reply other threads:[~2013-12-24 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 1:05 Surya Nimmagadda [this message]
2013-12-24 7:19 ` Daniel Kaminsky
2013-12-24 9:03 ` Surya Nimmagadda
2014-01-02 14:27 ` Thomas Monjalon
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=4f69b88f0cab464faee28a2f27988852@CO1PR05MB284.namprd05.prod.outlook.com \
--to=nscsekhar@juniper.net \
--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).