Intel DPDK - can't get started: Embedded Community

Up to Discussions in Software & Bios

19 Replies Last post: Mar 6, 2012 9:22 AM by cristian

hynese

12 posts since Jun 28, 2011

Currently Being Moderated

Jan 24, 2012 10:00 AM

Intel DPDK - can't get started

Greetings,

When I build and run the "helloworld" program, I get the following run-time error:

sudo ./helloworld -c 0xf -n 3 -m 2048
EAL: coremask set to f
EAL: Detected lcore 0 on socket 0
EAL: Detected lcore 1 on socket 1
EAL: Detected lcore 2 on socket 0
EAL: Detected lcore 3 on socket 1
EAL: Detected lcore 4 on socket 0
EAL: Detected lcore 5 on socket 1
EAL: Detected lcore 6 on socket 0
EAL: Detected lcore 7 on socket 1
EAL: Detected lcore 8 on socket 0
EAL: Detected lcore 9 on socket 1
EAL: Detected lcore 10 on socket 0
EAL: Detected lcore 11 on socket 1
EAL: Detected lcore 12 on socket 0
EAL: Detected lcore 13 on socket 1
EAL: Detected lcore 14 on socket 0
EAL: Detected lcore 15 on socket 1
EAL: Skip lcore 16 (not detected)
EAL: Skip lcore 17 (not detected)
EAL: Skip lcore 18 (not detected)
EAL: Skip lcore 19 (not detected)
EAL: Skip lcore 20 (not detected)
EAL: Skip lcore 21 (not detected)
EAL: Skip lcore 22 (not detected)
EAL: Skip lcore 23 (not detected)
EAL: check hugetlbfs
EAL: rte_memzone_reserve(): No appropriate segment found
RING: Cannot reserve memory
EAL: rte_eal_common_log_init(): cannot create log_history mempool
PANIC in rte_eal_init():
Cannot init logs
6: [./helloworld() [0x401649]]
5: [/lib/libc.so.6(__libc_start_main+0xfd) [0x7fb792f03c4d]]
4: [./helloworld() [0x401746]]
3: [./helloworld() [0x402012]]
2: [./helloworld() [0x4049d0]]
1: [./helloworld() [0x4048b6]]
Aborted

I simply do not understand these errors... Please help!

According to the getting started guide, the output should look like:

sudo ./build/app/helloworld -c 0xf -n 3 -m 2048
[sudo] password for rte:
EAL: coremask set to f
EAL: Detected lcore 0 on socket 0
EAL: Detected lcore 1 on socket 1
EAL: Detected lcore 2 on socket 0
EAL: Detected lcore 3 on socket 1
EAL: Detected lcore 4 on socket 0
EAL: Detected lcore 5 on socket 1
EAL: Detected lcore 6 on socket 0
EAL: Detected lcore 7 on socket 1
EAL: Detected lcore 8 on socket 0
EAL: Detected lcore 9 on socket 1
EAL: Detected lcore 10 on socket 0
EAL: Detected lcore 11 on socket 1
EAL: Detected lcore 12 on socket 0
EAL: Detected lcore 13 on socket 1
EAL: Detected lcore 14 on socket 0
EAL: Detected lcore 15 on socket 1
EAL: Detected lcore 16 on socket 0
EAL: Detected lcore 17 on socket 1
EAL: Detected lcore 18 on socket 0
EAL: Detected lcore 19 on socket 1
EAL: Detected lcore 20 on socket 0
EAL: Detected lcore 21 on socket 1
EAL: Detected lcore 22 on socket 0
EAL: Detected lcore 23 on socket 1
EAL: check hugetlbfs
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0add800000 (size = 0x200000)
EAL: Ask a virtual area of 0x3d400000 bytes
EAL: Virtual area found at 0x7f0aa0200000 (size = 0x3d400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0a9fc00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0a9f600000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0a9f000000 (size = 0x400000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f0a9e600000 (size = 0x800000)
EAL: Ask a virtual area of 0x800000 bytes

EAL: Virtual area found at 0x7f0a9dc00000 (size
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0a9d600000 (size
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0a9d000000 (size
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0a9ca00000 (size
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0a9c600000 (size
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0a9c200000 (size
EAL: Ask a virtual area of 0x3fc00000 bytes
EAL: Virtual area found at 0x7f0a5c400000 (size
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0a5c000000 (size
EAL: check igb_uio module
EAL: check module finished
EAL: Master core 0 is ready (tid=de25b700)
EAL: Core 1 is ready (tid=5b7fe700)
EAL: Core 3 is ready (tid=5a7fc700)
EAL: Core 2 is ready (tid=5affd700)
hello from core 1
hello from core 2
hello from core 3
hello from core 0

Tags: dpdk

muthurajanjayakumar

4 posts since
Jul 26, 2011

Currently Being Moderated

Jan 24, 2012 11:09 PM

in response to: hynese

Re: Intel DPDK - can't get started

Dear Eamonn Hynese,

Sorry for the inconvenience.

1) I see you are running with parameters for memory allocation. Can I please request you to run with default DPDK memory allocation?

Basically sudo ./helloworld -c 0x01

Please let me know what you observe?

(ps: Please find attached Release notes where section 8.4 - documents similar observation with respect to huge page allocation)

2) Also,can you please let me know what version of DPDK you are running? Will help me to forward corresponding documentations going over the reasoning for memory allocation. (ps: The second document I am attaching the test report which shows the tests and command line options that are used and documented for your reference. You will see the document indicating sudo ./helloworld -c 0x0f using the default DPDK memory allocation)

3) Since you have NUMA machine, wanted to check with you if you are doing explicit reservation of pages on each socket as follows? Please let me know in case you are able to do the following steps before running the application?

echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages

echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages

4) Can you please find out the number of pages allocated by giving the command and let us know what you get for the following command?

cat /proc/meminfo | grep Huge

5) What do you see when you look in the directory /dev/huge? (you will see n number of 2M Page files).

With respect and best regards,

M Jay

Attachments:

450257_DPDK_Test_Report_Rev0.7.pdf (4.2 MB)
450246_DPDK_Rel_Notes_Rev1.0.pdf (204.4 K)

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Jan 25, 2012 2:46 AM

in response to: muthurajanjayakumar

Re: Intel DPDK - can't get started

Hi M Jay,

Many thanks for your detailed response. I somehow managed to get it all working by using the setup.sh script in the "tools" menu. This seems to have done everything I require. I am using Ubuntu 10.04 LTS with a slightly upgraded kernel (2.6.34).

I'm still very new to the DPDK and still trying to get my head around things.

When I run `sudo ./helloworld -c 0x01` as you requested, I now get:

sudo ./helloworld -c 0x1
EAL: coremask set to 1
EAL: Detected lcore 0 on socket 0
EAL: Detected lcore 1 on socket 1
EAL: Detected lcore 2 on socket 0
EAL: Detected lcore 3 on socket 1
EAL: Detected lcore 4 on socket 0
EAL: Detected lcore 5 on socket 1
EAL: Detected lcore 6 on socket 0
EAL: Detected lcore 7 on socket 1
EAL: Detected lcore 8 on socket 0
EAL: Detected lcore 9 on socket 1
EAL: Detected lcore 10 on socket 0
EAL: Detected lcore 11 on socket 1
EAL: Detected lcore 12 on socket 0
EAL: Detected lcore 13 on socket 1
EAL: Detected lcore 14 on socket 0
EAL: Detected lcore 15 on socket 1
EAL: check hugetlbfs
EAL: Ask a virtual area of 0x7f000000 bytes
EAL: Virtual area found at 0x7f788b400000 (size = 0x7f000000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f788a600000 (size = 0xc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f788a200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f7889e00000 (size = 0x200000)
EAL: Ask a virtual area of 0x80000000 bytes
EAL: Virtual area found at 0x7f7809c00000 (size = 0x80000000)
EAL: check igb_uio module
EAL: check module finished
EAL: Master core 0 is ready (tid=ac3f700)
hello from core 0

It's working...

Thanks again.

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Jan 25, 2012 7:42 AM

in response to: hynese

Re: Intel DPDK - can't get started

OK, I've encountered another problem when trying to run the setup.sh script.

I've gone through all the steps - selected [4], [5], [7], [8] successfully.

But when I got to run [9], I get the following error: "No probed ethernet devices"

I even upgraded the driver of my network card to igb-3.3.6.

Here's an output from `lspci | grep Ethernet`
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
06:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
06:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
0b:00.0 Ethernet controller: Intel Corporation Device 1526 (rev 01)
0b:00.1 Ethernet controller: Intel Corporation Device 1526 (rev 01)
0c:00.0 Ethernet controller: Intel Corporation Device 1526 (rev 01)
0c:00.1 Ethernet controller: Intel Corporation Device 1526 (rev 01)

I'm definitely using the Intel NIC.

----------------------------------------------------------
Step 1: Select the DPDK environment to build
----------------------------------------------------------
[1] i686-default-linuxapp-gcc
[2] i686-default-linuxapp-icc
[3] x86_64-default-linuxapp-gcc
[4] x86_64-default-linuxapp-icc

----------------------------------------------------------
Step 2: Setup linuxapp environment
----------------------------------------------------------
[5] Insert IGB UIO module
[6] Setup hugepage mappings for non-NUMA systems
[7] Setup hugepage mappings for NUMA systems

----------------------------------------------------------
Step 3: Run test application for linuxapp environment
----------------------------------------------------------
[8] Run test application ($RTE_TARGET/app/test)
[9] Run testpmd application in interactive mode ($RTE_TARGET/app/testpmd)

----------------------------------------------------------
Step 4: Other tools
----------------------------------------------------------
[10] List hugepage info from /proc/meminfo
[11] List hugepage files in /mnt/huge

----------------------------------------------------------
Step 5: Uninstall and system cleanup
----------------------------------------------------------
[12] Uninstall all targets
[13] Remove IGB UIO module
[14] Remove hugepage mappings

[15] Exit Script

Option: 9

Enter hex bitmask of cores to execute testpmd app on
Example: to execute app on cores 0 to 7, enter 0xff
bitmask: ff
Launching app
EAL: coremask set to ff
EAL: Detected lcore 0 on socket 0
EAL: Detected lcore 1 on socket 1
EAL: Detected lcore 2 on socket 0
EAL: Detected lcore 3 on socket 1
EAL: Detected lcore 4 on socket 0
EAL: Detected lcore 5 on socket 1
EAL: Detected lcore 6 on socket 0
EAL: Detected lcore 7 on socket 1
EAL: Detected lcore 8 on socket 0
EAL: Detected lcore 9 on socket 1
EAL: Detected lcore 10 on socket 0
EAL: Detected lcore 11 on socket 1
EAL: Detected lcore 12 on socket 0
EAL: Detected lcore 13 on socket 1
EAL: Detected lcore 14 on socket 0
EAL: Detected lcore 15 on socket 1
EAL: check hugetlbfs
EAL: Ask a virtual area of 0x4a400000 bytes
EAL: Virtual area found at 0x7f79b3000000 (size = 0x4a400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f79b2200000 (size = 0xc00000)
EAL: Ask a virtual area of 0x2000000 bytes
EAL: Virtual area found at 0x7f79b0000000 (size = 0x2000000)
EAL: Ask a virtual area of 0x8c00000 bytes
EAL: Virtual area found at 0x7f79a7200000 (size = 0x8c00000)
EAL: Ask a virtual area of 0x9000000 bytes
EAL: Virtual area found at 0x7f799e000000 (size = 0x9000000)
EAL: Ask a virtual area of 0x9000000 bytes
EAL: Virtual area found at 0x7f7994e00000 (size = 0x9000000)
EAL: Ask a virtual area of 0x9000000 bytes
EAL: Virtual area found at 0x7f798bc00000 (size = 0x9000000)
EAL: Ask a virtual area of 0x2400000 bytes
EAL: Virtual area found at 0x7f7989600000 (size = 0x2400000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7f7988400000 (size = 0x1000000)
EAL: Ask a virtual area of 0xc000000 bytes
EAL: Virtual area found at 0x7f797c200000 (size = 0xc000000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f797be00000 (size = 0x200000)
EAL: Ask a virtual area of 0x38400000 bytes
EAL: Virtual area found at 0x7f7943800000 (size = 0x38400000)
EAL: Ask a virtual area of 0x1c000000 bytes
EAL: Virtual area found at 0x7f7927600000 (size = 0x1c000000)
EAL: Ask a virtual area of 0xec00000 bytes
EAL: Virtual area found at 0x7f7918800000 (size = 0xec00000)
EAL: Ask a virtual area of 0x1800000 bytes
EAL: Virtual area found at 0x7f7916e00000 (size = 0x1800000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f7916800000 (size = 0x400000)
EAL: Ask a virtual area of 0x6400000 bytes
EAL: Virtual area found at 0x7f7910200000 (size = 0x6400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f790fc00000 (size = 0x400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f790ee00000 (size = 0xc00000)
EAL: Ask a virtual area of 0x10400000 bytes
EAL: Virtual area found at 0x7f78fe800000 (size = 0x10400000)
EAL: Ask a virtual area of 0x3800000 bytes
EAL: Virtual area found at 0x7f78fae00000 (size = 0x3800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f78faa00000 (size = 0x200000)
EAL: check igb_uio module
EAL: check module finished
EAL: Master core 0 is ready (tid=fdcc8700)
EAL: Core 4 is ready (tid=f89fb700)
EAL: Core 1 is ready (tid=fa1fe700)
EAL: Core 6 is ready (tid=f79f9700)
EAL: Core 5 is ready (tid=f81fa700)
PANIC in main():
No probed ethernet devices - check that CONFIG_RTE_LIBRTE_82576_PMD=y and that CONFIG_RTE_LIBRTE_82599_PMD=y in your configuration file
EAL: Core 3 is ready (tid=f91fc700)
EAL: Core 2 is ready (tid=f99fd700)
EAL: Core 7 is ready (tid=f71f8700)
5: [x86_64-default-linuxapp-gcc/app/testpmd() [0x401b19]]
4: [/lib/libc.so.6(__libc_start_main+0xfd) [0x7f79fd531c4d]]
3: [x86_64-default-linuxapp-gcc/app/testpmd() [0x40354e]]
2: [x86_64-default-linuxapp-gcc/app/testpmd() [0x42e280]]
1: [x86_64-default-linuxapp-gcc/app/testpmd() [0x42e166]]
Aborted

Report Abuse

vincentjardin

5 posts since
Mar 22, 2011

Currently Being Moderated

Jan 25, 2012 3:30 PM

in response to: hynese

Re: Intel DPDK - can't get started

Your PCI 1526 (82576 Quad port copper board) device is not probed by the librte. Upgrading the Kernel igb driver will not help.

I strongly advise that you contact some support engineers at Intel or 6WIND if you need a patch.

Best regards,

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Jan 25, 2012 8:26 PM

in response to: vincentjardin

Re: Intel DPDK - can't get started

Greetings,

Many thanks for your useful reply. Hopefully I can get this sorted by contacting my Intel contact or 6WIND.

I did a fair bit of research before purchasing this NIC and hopefully it's compatible with the DPDK!

If anyone else has any suggestions, they're greatly receieved.

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Feb 1, 2012 9:56 AM

in response to: hynese

Re: Intel DPDK - can't get started

Greetings,

I haven't made any progress on this issue, but I do have some updates. I think this may be an issue related to NAPI?

When I try to make the igb driver with NAPI support, I get:

`sudo make CFLAGS_EXTRA=--DE1000_NAPI`

"This driver is not supported on kernel versions older than 2.4.21, because this driver requires NAPI support"

I'm using the igb driver version 3.3.6. Network card is Intel Kawela 82576 Quad port.

On Ubuntu 10.04 LTS, with kernel 2.6.34.

Still getting the errors when I try to run the tests:

Option: 9

Enter hex bitmask of cores to execute testpmd app on
Example: to execute app on cores 0 to 7, enter 0xff
bitmask: f
Launching app
EAL: coremask set to f
EAL: Detected lcore 0 on socket 0
EAL: Detected lcore 1 on socket 1
EAL: Detected lcore 2 on socket 0
EAL: Detected lcore 3 on socket 1
EAL: Detected lcore 4 on socket 0
EAL: Detected lcore 5 on socket 1
EAL: Detected lcore 6 on socket 0
EAL: Detected lcore 7 on socket 1
EAL: Detected lcore 8 on socket 0
EAL: Detected lcore 9 on socket 1
EAL: Detected lcore 10 on socket 0
EAL: Detected lcore 11 on socket 1
EAL: Detected lcore 12 on socket 0
EAL: Detected lcore 13 on socket 1
EAL: Detected lcore 14 on socket 0
EAL: Detected lcore 15 on socket 1
EAL: check hugetlbfs
EAL: Ask a virtual area of 0x80000000 bytes
EAL: Virtual area found at 0x7f7fbfe00000 (size = 0x80000000)
EAL: Ask a virtual area of 0x80000000 bytes
EAL: Virtual area found at 0x7f7f3fc00000 (size = 0x80000000)
EAL: check igb_uio module
EAL: check module finished
EAL: Master core 0 is ready (tid=40d1b700)
EAL: Core 1 is ready (tid=3f3fe700)
EAL: Core 2 is ready (tid=3ebfd700)
EAL: Core 3 is ready (tid=3e3fc700)
PANIC in main():
No probed ethernet devices - check that CONFIG_RTE_LIBRTE_82576_PMD=y and that CONFIG_RTE_LIBRTE_82599_PMD=y in your configuration file
4: [x86_64-default-linuxapp-icc/app/testpmd() [0x401ad9]]
3: [/lib/libc.so.6(__libc_start_main+0xfd) [0x7f80400ebc4d]]
2: [x86_64-default-linuxapp-icc/app/testpmd() [0x402d05]]
1: [x86_64-default-linuxapp-icc/app/testpmd() [0x4362a0]]
Aborted

Report Abuse

muthurajanjayakumar

4 posts since
Jul 26, 2011

Currently Being Moderated

Feb 2, 2012 5:38 PM

in response to: hynese

Re: Intel DPDK - can't get started

Can I please request to issue the command lspci and find out the list of PCIe Ethernet devices. This will help to see if the device type is recognized. See below the device IDs listed for your reference.

Please refer to release note. Can you please make sure the device type is in test_pci.c once you get the application running as shown in release notes “ref: pci_autotest in test application may not work

Update the /app/test/test_pci.c file with device ID found on the system”

E43709-xxx	Intel® Gigabit ET Dual Port Server Adapter	E1G42ET E1G42ETBLK	2 Ports, RJ45, 10/100/1000, PCI-e, 82576 VendorID:8086, DevID:10C9	Latest drivers
E31745-xxx	Intel® Gigabit EF Dual Port Server Adapter	E1G42EF E1G42EFBLK	2 Ports, LC, 1000, PCI-e, 82576 VendorID:8086, DevID:10E6	Latest drivers
E64750-xxx	Intel® Gigabit ET Quad Port Server Adapter	E1G44ET E1G44ETBLK	4 Ports, RJ45, 10/100/1000, PCI-e, 82576 VendorID:8086, DevID: 10E8	Latest drivers
E91609-xxx	Intel® Gigabit ET2 Quad Port Server Adapter	E1G44ET2 E1G44ET2BLK	4 Ports, RJ45, 10/100/1000, PCI-e, 82576 VendorID:8086, DevID: 1526	Latest

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Feb 3, 2012 4:47 AM

in response to: muthurajanjayakumar

Re: Intel DPDK - can't get started

Hi Muthura,

Many thanks for your reply. I've just got into the office now, hence my late reply.

Here is the output of lspci:

lspci
00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13)
00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 2 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13)
00:04.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 4 (rev 13)
00:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5 (rev 13)
00:06.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 6 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13)
00:08.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 8 (rev 13)
00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 13)
00:0a.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 10 (rev 13)
00:0d.0 Host bridge: Intel Corporation Device 343a (rev 13)
00:0d.1 Host bridge: Intel Corporation Device 343b (rev 13)
00:0d.2 Host bridge: Intel Corporation Device 343c (rev 13)
00:0d.3 Host bridge: Intel Corporation Device 343d (rev 13)
00:0d.4 Host bridge: Intel Corporation 5520/5500/X58 Physical Layer Port 0 (rev 13)
00:0d.5 Host bridge: Intel Corporation 5520/5500 Physical Layer Port 1 (rev 13)
00:0d.6 Host bridge: Intel Corporation Device 341a (rev 13)
00:0e.0 Host bridge: Intel Corporation Device 341c (rev 13)
00:0e.1 Host bridge: Intel Corporation Device 341d (rev 13)
00:0e.2 Host bridge: Intel Corporation Device 341e (rev 13)
00:0e.3 Host bridge: Intel Corporation Device 341f (rev 13)
00:0e.4 Host bridge: Intel Corporation Device 3439 (rev 13)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13)
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.3 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIB (ICH10) LPC Interface Controller
00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller #1
01:03.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
02:00.0 System peripheral: Hewlett-Packard Company iLO3 Slave instrumentation & System support (rev 04)
02:00.2 System peripheral: Hewlett-Packard Company iLO3 Management Processor Support and Messaging (rev 04)
02:00.4 USB Controller: Hewlett-Packard Company Proliant iLO2 virtual USB controller (rev 01)
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
05:00.0 RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01)
06:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
06:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
09:00.0 PCI bridge: Integrated Device Technology, Inc. PES12N3A PCI Express Switch (rev 0c)
0a:02.0 PCI bridge: Integrated Device Technology, Inc. PES12N3A PCI Express Switch (rev 0c)
0a:04.0 PCI bridge: Integrated Device Technology, Inc. PES12N3A PCI Express Switch (rev 0c)
0b:00.0 Ethernet controller: Intel Corporation Device 1526 (rev 01)
0b:00.1 Ethernet controller: Intel Corporation Device 1526 (rev 01)
0c:00.0 Ethernet controller: Intel Corporation Device 1526 (rev 01)
0c:00.1 Ethernet controller: Intel Corporation Device 1526 (rev 01)

And here is the relevant part from lshw:

description: Ethernet interface
                      product: Intel Corporation
                      vendor: Intel Corporation
                      physical id: 0
                      bus info: pci@0000:0c:00.0
                      logical name: eth6
                      version: 01
                      serial: 00:1b:21:d2:93:56
                      width: 32 bits
                      clock: 33MHz
                      capabilities: bus_master cap_list ethernet physical
                      configuration: broadcast=yes driver=igb driverversion=3.3.6 firmware=1.2-1 ip=172.20.3.254 latency=0 multicast=yes
                      resources: irq:24 memory:fbfe0000-fbffffff memory:fb800000-fbbfffff ioport:6000(size=32) memory:fb7f0000-fb7f3fff memory:df200000-df21ffff memory:df220000-df23ffff

I'm using the Intel card over eth6 with no problems, until it comes to the DPDK stuff.

I opened up ./app/test/test_pci.c and interestingly my card (82576) is listed as being under the e1000_hw.h:

/* From e1000_hw.h */
#define E1000_DEV_ID_82576                    0x10C9
#define E1000_DEV_ID_82576_FIBER              0x10E6
#define E1000_DEV_ID_82576_SERDES             0x10E7
#define E1000_DEV_ID_82576_QUAD_COPPER        0x10E8
#define E1000_DEV_ID_82576_QUAD_COPPER_ET2    0x1526
#define E1000_DEV_ID_82576_NS                 0x150A
#define E1000_DEV_ID_82576_NS_SERDES          0x1518
#define E1000_DEV_ID_82576_SERDES_QUAD        0x150D
#define E1000_DEV_ID_82576_VF                 0x10CA
#define E1000_DEV_ID_I350_VF                  0x1520
#define E1000_DEV_ID_82575EB_COPPER           0x10A7
#define E1000_DEV_ID_82575EB_FIBER_SERDES     0x10A9
#define E1000_DEV_ID_82575GB_QUAD_COPPER      0x10D6
#define E1000_DEV_ID_82580_COPPER             0x150E
#define E1000_DEV_ID_82580_FIBER              0x150F
#define E1000_DEV_ID_82580_SERDES             0x1510
#define E1000_DEV_ID_82580_SGMII              0x1511
#define E1000_DEV_ID_82580_COPPER_DUAL        0x1516
#define E1000_DEV_ID_82580_QUAD_FIBER         0x1527
#define E1000_DEV_ID_I350_COPPER              0x1521
#define E1000_DEV_ID_I350_FIBER               0x1522
#define E1000_DEV_ID_I350_SERDES              0x1523
#define E1000_DEV_ID_I350_SGMII               0x1524
#define E1000_DEV_ID_I350_DA4                 0x1546
#define E1000_DEV_ID_DH89XXCC_SGMII           0x0438
#define E1000_DEV_ID_DH89XXCC_SERDES          0x043A
#define E1000_DEV_ID_DH89XXCC_BACKPLANE       0x043C
#define E1000_DEV_ID_DH89XXCC_SFP             0x0440

/* From ixgbe_hw.h */
#define IXGBE_DEV_ID_82598                 0x10B6
#define IXGBE_DEV_ID_82598_BX              0x1508
#define IXGBE_DEV_ID_82598AF_DUAL_PORT     0x10C6
#define IXGBE_DEV_ID_82598AF_SINGLE_PORT   0x10C7
#define IXGBE_DEV_ID_82598AT               0x10C8
#define IXGBE_DEV_ID_82598AT2              0x150B
#define IXGBE_DEV_ID_82598EB_SFP_LOM       0x10DB
#define IXGBE_DEV_ID_82598EB_CX4           0x10DD
#define IXGBE_DEV_ID_82598_CX4_DUAL_PORT   0x10EC
#define IXGBE_DEV_ID_82598_DA_DUAL_PORT    0x10F1
#define IXGBE_DEV_ID_82598_SR_DUAL_PORT_EM 0x10E1
#define IXGBE_DEV_ID_82598EB_XF_LR         0x10F4
#define IXGBE_DEV_ID_82599_KX4             0x10F7
#define IXGBE_DEV_ID_82599_CX4             0x10F9
#define IXGBE_DEV_ID_82599_SFP             0x10FB
#define IXGBE_DEV_ID_82599_XAUI_LOM        0x10FC

Should I be using the e1000 driver? I'm going to try this now.

Report Abuse

muthurajanjayakumar

4 posts since
Jul 26, 2011

Currently Being Moderated

Feb 3, 2012 6:29 PM

in response to: hynese

Re: Intel DPDK - can't get started

Hi,

What version of DPDK s/w you are using? Is it R1.0? or R1.1?

Please let me know

Thanks,

M Jay

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Feb 4, 2012 2:34 AM

in response to: muthurajanjayakumar

Re: Intel DPDK - can't get started

HI M Jay,

I'm using 473333_DPDK.L.1.1.0_27

Thanks,

Eamonn

Report Abuse

muthurajanjayakumar

4 posts since
Jul 26, 2011

Currently Being Moderated

Feb 6, 2012 1:42 PM

in response to: hynese

Re: Intel DPDK - can't get started

Dear Eamonn,

That is the latest one.

Can I please request you to kindly run without the NAPI option.

Thanks,

M. Jay

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Feb 7, 2012 3:01 AM

in response to: muthurajanjayakumar

Re: Intel DPDK - can't get started

Hi M Jay,

I've tried it using with NAPI disabled and I get the same results.

Do you think I could set up a call with you at some convenient time? I'm on GMT time.

Many thanks,

Eamonn

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Mar 5, 2012 9:59 AM

in response to: muthurajanjayakumar

Re: Intel DPDK - can't get started

Greetings,

I haven't been doing much DPDK stuff in a few weeks now. I'm back on it now and still having similar problems.

I made those modifications to /app/test/test_pci.c as outlined in the release notes (shown below).

{

.vendor_id = 0x8086,

.device_id = 0x1526,

.subsystem_vendor_id = PCI_ANY_ID,

.subsystem_device_id = PCI_ANY_ID,

}

When I run source ./tests/setup.sh and choose option 8, I get the following error:

Scan bus

EAL: probe driver: 8086:1526 test_driver

EAL: unbind kernel driver /sys/bus/pci/devices/0000:0b:00.0/driver/unbind

EAL: bind PCI device 0000:0b:00.0 to uio driver

EAL: Device bound

EAL: map PCI resource for device 0000:0b:00.0

EAL: PCI memory mapped at 0x7f57cdb42000

My driver init called

0:b:0.0 - vendor:8086 device:1526

EAL: probe driver: 8086:1526 test_driver

EAL: unbind kernel driver /sys/bus/pci/devices/0000:0b:00.1/driver/unbind

***SYSTEM TOTALLY FREEZES HERE***

The system totally freezes, I lose my ssh connection and I have to go down to the server room to restart the machine (/etc/init.d/networking restart doesn't work, nor does reinstalling the igb driver).

I'm really stuck again.

Report Abuse

cristian

3 posts since
Mar 5, 2012

Currently Being Moderated

Mar 5, 2012 1:33 PM

in response to: hynese

Re: Intel DPDK - can't get started

When the DPDK app is started, it tries to get control over all the ports in the system that it can probe. So, if you are connected to the board through a network connection (most likely SSH), then when DPDK is started it will recognize that NIC as supported and proceed to remove it from the list of devices handled by the Linux kernel. This results in you losing connectivity with your board.

This is actually documented in the release notes. The possible workarounds are:

1. Use for network connectivity a NIC that is not supported by DPDK (e.g. old Intel NIC or non-Intel NIC)

-- or --

2. Remove the PCI device ID from the list of supported devices in teh source code. Siply grep for it and delete it, you will probaly find it several times in different files.

This is fixed in the next DPDK release. There will be a port "black list" feature to specify which devices to be kept away from DPDK.

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Mar 6, 2012 4:22 AM

in response to: cristian

Re: Intel DPDK - can't get started

Hi cristian,

Very useful observations there.

I'm going to go with suggestion 1. and use eth0 (a Broadcom NIC) for network connectivity.

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Mar 6, 2012 5:32 AM

in response to: cristian

Re: Intel DPDK - can't get started

Hi cristian,

I have the following ifconfig:

eth0 Link encap:Ethernet HWaddr 3c:d9:2b:f9:0d:80

inet addr:172.20.3.254 Bcast:172.20.3.255 Mask:255.255.255.128

inet6 addr: fe80::3ed9:2bff:fef9:d80/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:16238 errors:0 dropped:0 overruns:0 frame:0

TX packets:13338 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1329512 (1.3 MB) TX bytes:1249028 (1.2 MB)

Interrupt:30 Memory:ec000000-ec012800

eth6 Link encap:Ethernet HWaddr 00:1b:21:d2:93:56

inet addr:172.20.3.187 Bcast:172.20.3.255 Mask:255.255.255.128

inet6 addr: fe80::21b:21ff:fed2:9356/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:815741 errors:0 dropped:0 overruns:0 frame:0

TX packets:684654 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:194543668 (194.5 MB) TX bytes:240334118 (240.3 MB)

Memory:fbfe0000-fc000000

eth0 (Broadcom) is a static IP address and eth6 (Intel 82576) is assigned via DHCP.

I'm still getting the following error when running option 9 in `source ./tools/setup.sh`:

bitmask: 0xf

Launching app

EAL: coremask set to f

EAL: Detected lcore 0 on socket 0

EAL: Detected lcore 1 on socket 1

EAL: Detected lcore 2 on socket 0

EAL: Detected lcore 3 on socket 1

EAL: Detected lcore 4 on socket 0

EAL: Detected lcore 5 on socket 1

EAL: Detected lcore 6 on socket 0

EAL: Detected lcore 7 on socket 1

EAL: Detected lcore 8 on socket 0

EAL: Detected lcore 9 on socket 1

EAL: Detected lcore 10 on socket 0

EAL: Detected lcore 11 on socket 1

EAL: Detected lcore 12 on socket 0

EAL: Detected lcore 13 on socket 1

EAL: Detected lcore 14 on socket 0

EAL: Detected lcore 15 on socket 1

EAL: check hugetlbfs

EAL: Ask a virtual area of 0x200000 bytes

EAL: Virtual area found at 0x7f469d600000 (size = 0x200000)

EAL: Ask a virtual area of 0x3fc00000 bytes

EAL: Virtual area found at 0x7f465d800000 (size = 0x3fc00000)

EAL: Ask a virtual area of 0x200000 bytes

EAL: Virtual area found at 0x7f465d400000 (size = 0x200000)

EAL: Ask a virtual area of 0x40000000 bytes

EAL: Virtual area found at 0x7f461d200000 (size = 0x40000000)

EAL: check igb_uio module

EAL: check module finished

EAL: Master core 0 is ready (tid=9e0b0700)

EAL: Core 1 is ready (tid=1c9fe700)

EAL: Core 3 is ready (tid=1b9fc700)

PANIC in main():

No probed ethernet devices - check that CONFIG_RTE_LIBRTE_82576_PMD=y and that CONFIG_RTE_LIBRTE_82599_PMD=y in your configuration file

EAL: Core 2 is ready (tid=1c1fd700)

5: [x86_64-default-linuxapp-gcc/app/testpmd() [0x401b19]]

4: [/lib/libc.so.6(__libc_start_main+0xfd) [0x7f469d928c4d]]

3: [x86_64-default-linuxapp-gcc/app/testpmd() [0x40354e]]

2: [x86_64-default-linuxapp-gcc/app/testpmd() [0x42e280]]

1: [x86_64-default-linuxapp-gcc/app/testpmd() [0x42e166]]

Aborted

Report Abuse

cristian

3 posts since
Mar 5, 2012

Currently Being Moderated

Mar 6, 2012 7:32 AM

in response to: hynese

Re: Intel DPDK - can't get started

Accoring to the error message, looks like you either do not have any supported Intel NICs on your board at this point or you modified your code base to disable the 1GbE NIC and 10GbE NIC support in your system (in ./config/defconfig_XXX file options). Maybe it would be good to restart with a clean code base?

Report Abuse

hynese

12 posts since
Jun 28, 2011

Currently Being Moderated

Mar 6, 2012 7:56 AM

in response to: cristian

Re: Intel DPDK - can't get started

Hi Cristian,

Thanks for the tips. I unzipped a fresh DPDK and am still having the same problem.

I might try and get my hands on another Intel card. I was however, under the impression that the card we bought (82576) was DPDK compatible.

Eamonn

Report Abuse

cristian

3 posts since
Mar 5, 2012

Currently Being Moderated

Mar 6, 2012 9:22 AM

in response to: hynese

Re: Intel DPDK - can't get started

Hi Eamonn,

What is the device ID of your card? Intel 82576 is supported by the DPDK release 1.1 that you are using, but it might be that you need to add that specific PCI device ID to DPDK, as tehre are a multitude of flavors (each one with a different device ID) for each NIC model. We'll consolidate all the device IDs in a single file for the next release, but for 1.1 release I am afraid you have to add your device ID to the kernel module, PMD driver and pci atotest manually. For 1GbE NICs, this means the following files (similar files for 10GbE NICs):

lib/librte_eal/linuxapp/igb_uio.igb_uio.c

lib/librte_82576_pmd/igb/e1000_hw.h

app/test/test_pci.c

Please let me know if it works.

Report Abuse

Go to original post

Support Options

Design Assistance

Intel e-Help Forum

Chat Now

Jan 24, 2012 10:00 AM

Intel DPDK - can't get started

Actions

More Like This

Bookmarked By (0)