DPDK usage discussions
 help / color / mirror / Atom feed
From: Mohanraj Venkat <msvmohanraj@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Error "EAL: PCI device 0000:04:00.0 on NUMA socket -1 EAL: probe driver: 8086:1521 rte_igb_pmd" with uio_pci_generic driver in DPDK in box sponsered by intel
Date: Tue, 22 Nov 2016 16:18:21 +0530	[thread overview]
Message-ID: <CAH9UErVyKgErWH4-SPk0w-cDNfCeP=nm-WSFnb_i-A28Rb9a1w@mail.gmail.com> (raw)

Hi,

We are using DPDK in box (Minnowboard Turbot) sponsered by intel. We
installed dpdk as per the installation guide and did
modprobe uio_pci_generic.

We have used uio_pci_generic and successfully binded the NICs as below.



dpdk@dpdk-Minnowboard-Turbot-D0-PLATFORM:/usr/src/dpdk-16.07/tools$
./dpdk-devbind.py -s

Network devices using DPDK-compatible driver

============================================

0000:04:00.0 'I350 Gigabit Network Connection' drv=uio_pci_generic
unused=igb

0000:04:00.1 'I350 Gigabit Network Connection' drv=uio_pci_generic
unused=igb

Network devices using kernel driver

===================================

0000:03:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
if=enp3s0 drv=r8169 unused=uio_pci_generic *Active*



*Huge Page Configuration:*

-bash-4.3$ cat /proc/meminfo | grep Huge

AnonHugePages:    239616 kB

HugePages_Total:      64

HugePages_Free:        0

HugePages_Rsvd:        0

HugePages_Surp:        0

Hugepagesize:       2048 kB





But when we run “./testpmd” to do the basic testing, We are facing the
segmentation fault.



dpdk@dpdk-Minnowboard-Turbot-D0-PLATFORM:/usr/src/dpdk-16.07/x86_64-native-linuxapp-gcc/app/test

Launching app

EAL: Detected 2 lcore(s)

EAL: Probing VFIO support...

PMD: bnxt_rte_pmd_init() called for (null)

EAL: PCI device 0000:04:00.0 on NUMA socket -1

EAL:   probe driver: 8086:1521 rte_igb_pmd

Segmentation fault  (core dumped)



*GDB Debugging:*

Thread 1 "test" received signal SIGSEGV, Segmentation fault.

0x00000000005fa9b8 in eth_igb_dev_init ()

(gdb) bt

#0  0x00000000005fa9b8 in eth_igb_dev_init ()

#1  0x00000000005844f2 in rte_eth_dev_init ()

#2  0x000000000059b958 in pci_probe_all_drivers ()

#3  0x000000000059be24 in rte_eal_pci_probe ()

#4  0x0000000000590317 in rte_eal_init ()

#5  0x000000000042dd35 in main ()

(gdb) list

1       ../sysdeps/x86_64/dl-procinfo.c: No such file or directory.

(gdb)



Please help us to resolve this issue.

                 reply	other threads:[~2016-11-22 10:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAH9UErVyKgErWH4-SPk0w-cDNfCeP=nm-WSFnb_i-A28Rb9a1w@mail.gmail.com' \
    --to=msvmohanraj@gmail.com \
    --cc=users@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).