All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Sune <marc.sune-kpkqNMk1I7M@public.gmane.org>
To: "<dev-VfR2kkLFssw@public.gmane.org>" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Unusable interfaces although apparently attached to IGB_UIO
Date: Tue, 25 Feb 2014 13:20:06 +0100	[thread overview]
Message-ID: <530C8A76.5040701@bisdn.de> (raw)

Dear all,

We've been experiencing problems with interfaces being recognised by 
DPDK since some time now, I think since the very begining we started 
using DPDK (aprox. 1.3). Randomly, even on a fresh reboot (after 
modprobe->attach->launch dpdk_app), and properly attached to the IGB_UIO 
kmod [0], interfaces do appear in the "probe stage" of the respective 
driver during RTE* initialization, but DPDK complains there are no 
DPDK-enabled interfaces [1].

It even happens with the examples provided [1]. Once they enter in this 
"zombie state", there is no way to recover them unless a reboot is 
performed. Attaching igb_uio -> igb -> gb_uio does not solve it either. 
This happens also with 1G copper ports.

Any ideas?

Thanks and regards
marc

p.s. Using 1.5.2 branch right now

-------------------------

[0] setup.sh

Option: 10


Network devices using IGB_UIO driver
====================================
0000:06:00.0 '82599EB 10-Gigabit SFI/SFP+ Network Connection' 
drv=igb_uio unused=
0000:06:00.1 '82599EB 10-Gigabit SFI/SFP+ Network Connection' 
drv=igb_uio unused=

Network devices using kernel driver
===================================
0000:08:00.1 'DH8900CC Series Gigabit Network Connection' if=eth3 
drv=igb unused=igb_uio
0000:08:00.2 'DH8900CC Series Gigabit Network Connection' if=eth5 
drv=igb unused=igb_uio
0000:08:00.3 'DH8900CC Series Gigabit Network Connection' if=eth6 
drv=igb unused=igb_uio
0000:08:00.4 'DH8900CC Series Gigabit Network Connection' if=eth7 
drv=igb unused=igb_uio
0000:09:00.0 'I350 Gigabit Network Connection' if=eth8 drv=igb 
unused=igb_uio *Active*
0000:09:00.1 'I350 Gigabit Network Connection' if=eth9 drv=igb 
unused=igb_uio *Active*
0000:09:00.2 'I350 Gigabit Network Connection' if=eth10 drv=igb 
unused=igb_uio
0000:09:00.3 'I350 Gigabit Network Connection' if=eth11 drv=igb 
unused=igb_uio
0000:85:00.0 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=eth2 
drv=ixgbe unused=igb_uio
0000:85:00.1 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=eth4 
drv=ixgbe unused=igb_uio

Other network devices
=====================
<none>

Enter PCI address of device to bind to IGB UIO driver:


[1] l2fwd

marc@bertha-dpdk:~/dpdk/examples/l2fwd/build$ sudo ./l2fwd -c 0xFF -n 2
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 0 on socket 1
EAL: Detected lcore 9 as core 1 on socket 1
EAL: Detected lcore 10 as core 2 on socket 1
EAL: Detected lcore 11 as core 3 on socket 1
EAL: Detected lcore 12 as core 4 on socket 1
EAL: Detected lcore 13 as core 5 on socket 1
EAL: Detected lcore 14 as core 6 on socket 1
EAL: Detected lcore 15 as core 7 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: Skip lcore 24 (not detected)
EAL: Skip lcore 25 (not detected)
EAL: Skip lcore 26 (not detected)
EAL: Skip lcore 27 (not detected)
EAL: Skip lcore 28 (not detected)
EAL: Skip lcore 29 (not detected)
EAL: Skip lcore 30 (not detected)
EAL: Skip lcore 31 (not detected)
EAL: Skip lcore 32 (not detected)
EAL: Skip lcore 33 (not detected)
EAL: Skip lcore 34 (not detected)
EAL: Skip lcore 35 (not detected)
EAL: Skip lcore 36 (not detected)
EAL: Skip lcore 37 (not detected)
EAL: Skip lcore 38 (not detected)
EAL: Skip lcore 39 (not detected)
EAL: Skip lcore 40 (not detected)
EAL: Skip lcore 41 (not detected)
EAL: Skip lcore 42 (not detected)
EAL: Skip lcore 43 (not detected)
EAL: Skip lcore 44 (not detected)
EAL: Skip lcore 45 (not detected)
EAL: Skip lcore 46 (not detected)
EAL: Skip lcore 47 (not detected)
EAL: Skip lcore 48 (not detected)
EAL: Skip lcore 49 (not detected)
EAL: Skip lcore 50 (not detected)
EAL: Skip lcore 51 (not detected)
EAL: Skip lcore 52 (not detected)
EAL: Skip lcore 53 (not detected)
EAL: Skip lcore 54 (not detected)
EAL: Skip lcore 55 (not detected)
EAL: Skip lcore 56 (not detected)
EAL: Skip lcore 57 (not detected)
EAL: Skip lcore 58 (not detected)
EAL: Skip lcore 59 (not detected)
EAL: Skip lcore 60 (not detected)
EAL: Skip lcore 61 (not detected)
EAL: Skip lcore 62 (not detected)
EAL: Skip lcore 63 (not detected)
EAL: Setting up memory...
EAL: Ask a virtual area of 0x1073741824 bytes
EAL: Virtual area found at 0x7f7dff000000 (size = 0x40000000)
EAL: Ask a virtual area of 0x1073741824 bytes
EAL: Virtual area found at 0x7f7dbee00000 (size = 0x40000000)
EAL: Requesting 512 pages of size 2MB from socket 0
EAL: Requesting 512 pages of size 2MB from socket 1
EAL: TSC frequency is ~1200000 KHz
EAL: Master core 0 is ready (tid=4025a840)
EAL: Core 1 is ready (tid=be1f2700)
EAL: Core 4 is ready (tid=bc9ef700)
EAL: Core 6 is ready (tid=bb9ed700)
EAL: Core 3 is ready (tid=bd1f0700)
EAL: Core 7 is ready (tid=bb1ec700)
EAL: Core 5 is ready (tid=bc1ee700)
EAL: Core 2 is ready (tid=bd9f1700)
EAL: PCI device 0000:06:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f7e401a7000
EAL:   PCI memory mapped at 0x7f7e4026d000
EAL: PCI device 0000:06:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f7e40127000
EAL:   PCI memory mapped at 0x7f7e40269000
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL:   probe driver: 8086:438 rte_igb_pmd
EAL:   0000:08:00.1 not managed by UIO driver, skipping
EAL: PCI device 0000:08:00.2 on NUMA socket 0
EAL:   probe driver: 8086:438 rte_igb_pmd
EAL:   0000:08:00.2 not managed by UIO driver, skipping
EAL: PCI device 0000:08:00.3 on NUMA socket 0
EAL:   probe driver: 8086:438 rte_igb_pmd
EAL:   0000:08:00.3 not managed by UIO driver, skipping
EAL: PCI device 0000:08:00.4 on NUMA socket 0
EAL:   probe driver: 8086:438 rte_igb_pmd
EAL:   0000:08:00.4 not managed by UIO driver, skipping
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   0000:09:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   0000:09:00.1 not managed by UIO driver, skipping
EAL: PCI device 0000:09:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   0000:09:00.2 not managed by UIO driver, skipping
EAL: PCI device 0000:09:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   0000:09:00.3 not managed by UIO driver, skipping
EAL: PCI device 0000:85:00.0 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   0000:85:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:85:00.1 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   0000:85:00.1 not managed by UIO driver, skipping
EAL: Error - exiting with code: 1
   Cause: No Ethernet ports - bye

             reply	other threads:[~2014-02-25 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 12:20 Marc Sune [this message]
     [not found] ` <530C8A76.5040701-kpkqNMk1I7M@public.gmane.org>
2014-02-25 13:00   ` Unusable interfaces although apparently attached to IGB_UIO Ananyev, Konstantin
     [not found]     ` <2601191342CEEE43887BDE71AB97725808E6ACA7-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-02-25 13:27       ` Marc Sune
     [not found]         ` <530C9A46.2010504-kpkqNMk1I7M@public.gmane.org>
2014-02-25 13:36           ` Thomas Monjalon
2014-02-26 13:03           ` Ananyev, Konstantin

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=530C8A76.5040701@bisdn.de \
    --to=marc.sune-kpkqnmk1i7m@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.