[dpdk-dev] Illegal instruction at rte_malloc_socket

2013-12-24 Thread Surya Nimmagadda
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 :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

:00:03.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
:00:04.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000

Network devices using kernel driver
===
:00:05.0 '82540EM Gigabit Ethernet Controller' if=eth2 drv=e1000 
unused=igb_uio
:00:06.0 '82540EM Gigabit Ethernet Controller' if=eth3 drv=e1000 
unused=igb_uio *Active*




[dpdk-dev] Illegal instruction at rte_malloc_socket

2013-12-24 Thread Daniel Kaminsky
Did you run the program using "sudo"?

Daniel Kaminsky

Sent from my iPhone

On Dec 24, 2013, at 3:05 AM, Surya Nimmagadda  wrote:

> 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 :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
> 
> :00:03.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
> :00:04.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
> 
> Network devices using kernel driver
> ===
> :00:05.0 '82540EM Gigabit Ethernet Controller' if=eth2 drv=e1000 
> unused=igb_uio
> :00:06.0 '82540EM Gigabit Ethernet Controller' if=eth3 drv=e1000 
> unused=igb_uio *Active*
> 
> 


[dpdk-dev] Illegal instruction at rte_malloc_socket

2013-12-24 Thread Surya Nimmagadda
Yeah. I did.

Thanks
Surya



 Original message 
From: Daniel Kaminsky 
Date: 12/23/2013 11:23 PM (GMT-08:00)
To: Surya Nimmagadda 
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] Illegal instruction at rte_malloc_socket


Did you run the program using "sudo"?

Daniel Kaminsky

Sent from my iPhone

On Dec 24, 2013, at 3:05 AM, Surya Nimmagadda mailto:nscsekhar at juniper.net>> wrote:

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 :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

:00:03.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
:00:04.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000

Network devices using kernel driver
===
:00:05.0 '82540EM Gigabit Ethernet Controller' if=eth2 drv=e1000 
unused=igb_uio
:00:06.0 '82540EM Gigabit Ethernet Controller' if=eth3 drv=e1000 
unused=igb_uio *Active*