From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 86] Requested device cannot be used
Date: Tue, 28 Aug 2018 02:18:35 +0000 [thread overview]
Message-ID: <bug-86-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=86
Bug ID: 86
Summary: Requested device cannot be used
Product: DPDK
Version: unspecified
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: tcnieh@iii.org.tw
Target Milestone: ---
Hello all,
I am trying to get the performance of intel x520 10G NIC over Dell R630/R730,
but I keep getting an unexpected error, please see below.
I followed the instruction of https://goo.gl/T7iTuk to compiler the DPDK and
OVS code. I've successfully binded both my x520 NIC ports to DPDK, using either
igb_uio or vfio_pci:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Network devices using DPDK-compatible driver
============================================
0000:82:00.0 'Ethernet 10G 2P X520 Adapter 154d' drv=igb_uio unused=vfio-pci
0000:82:00.1 'Ethernet 10G 2P X520 Adapter 154d' drv=igb_uio unused=vfio-pci
Network devices using kernel driver
===================================
0000:01:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=eno1 drv=tg3
unused=igb_uio,vfio-pci
0000:01:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=eno2 drv=tg3
unused=igb_uio,vfio-pci
0000:02:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=eno3 drv=tg3
unused=igb_uio,vfio-pci
0000:02:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=eno4 drv=tg3
unused=igb_uio,vfio-pci *Active*
Other Network devices
=====================
<none>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
And the hugepage was set to 2048 * 2M
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HugePages_Total: 2048
HugePages_Free: 1024
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Here comes the problem, while I tried to init the ovsdb-server and ovs-vswitch,
I got the following error:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2018-08-27T09:54:05.548Z|00002|ovs_numa|INFO|Discovered 16 CPU cores on NUMA
node 0
2018-08-27T09:54:05.548Z|00003|ovs_numa|INFO|Discovered 16 CPU cores on NUMA
node 1
2018-08-27T09:54:05.548Z|00004|ovs_numa|INFO|Discovered 2 NUMA nodes and 32
CPU cores
2018-08-27T09:54:05.548Z|00005|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
connecting...
2018-08-
27T09:54:05.549Z|00006|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
connected
2018-08-27T09:54:05.552Z|00007|dpdk|INFO|DPDK Enabled - initializing...
2018-08-27T09:54:05.552Z|00008|dpdk|INFO|No vhost-sock-dir provided -
defaulting to /usr/local/var/run/openvswitch
2018-08-27T09:54:05.552Z|00009|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem
1024,0 -c 0x00000001
2018-08-27T09:54:05.553Z|00010|dpdk|INFO|EAL: Detected 32 lcore(s)
2018-08-27T09:54:05.558Z|00011|dpdk|WARN|EAL: No free hugepages reported in
hugepages-1048576kB
2018-08-27T09:54:05.559Z|00012|dpdk|INFO|EAL: Probing VFIO support...
2018-08-27T09:54:06.700Z|00013|dpdk|INFO|EAL: PCI device 0000:82:00.0 on
NUMA socket 1
2018-08-27T09:54:06.700Z|00014|dpdk|INFO|EAL: probe driver: 8086:154d
net_ixgbe
2018-08-27T09:54:06.700Z|00015|dpdk|ERR|EAL: Requested device 0000:82:00.0
cannot be used
2018-08-27T09:54:06.700Z|00016|dpdk|INFO|EAL: PCI device 0000:82:00.1 on
NUMA socket 1
2018-08-27T09:54:06.700Z|00017|dpdk|INFO|EAL: probe driver: 8086:154d
net_ixgbe
2018-08-27T09:54:06.700Z|00018|dpdk|ERR|EAL: Requested device 0000:82:00.1
cannot be used
2018-08-27T09:54:06.701Z|00019|dpdk|INFO|DPDK Enabled - initialized
2018-08-27T09:54:06.705Z|00020|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath
supports recirculation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Therefore, I also got the same error when I added a dpdk-port:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2018-08-27T09:54:06.709Z|00036|dpdk|INFO|EAL: PCI device 0000:82:00.0 on NUMA
socket 1
2018-08-27T09:54:06.709Z|00037|dpdk|INFO|EAL: probe driver: 8086:154d
net_ixgbe
2018-08-27T09:54:06.710Z|00038|dpdk|WARN|EAL: Requested device 0000:82:00.0
cannot be used
2018-08-27T09:54:06.710Z|00039|dpdk|ERR|EAL: Driver cannot attach the device
(0000:82:00.0)
2018-08-27T09:54:06.710Z|00040|netdev_dpdk|WARN|Error attaching device
'0000:82:00.0' to DPDK
2018-08-27T09:54:06.710Z|00041|netdev|WARN|dpdk0: could not set configuration
(Invalid argument)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've tried a solution described in https://goo.gl/3opVRT, which is utilizing
"uio_pci_generic" and disable intel_iommu. It didn't work to me.
Here is detail info about my test platform:
DPDK & OVS version: DPDK 16.11 & OVS 2.7.0, DPDK 17.05.1 & OVS 2.8.0, DPDK
17.11 & OVS 2.9.0, DPDK 17.11 & OVS 2.10.0
OS: ubuntu 16.04
Hardware: Dell R730/R630 server with intel X520 10G NIC
128G Memory, 32 Cores.
Can anybody help or give me a hint to debug? I'm totally loss here.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-08-28 2:18 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=bug-86-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 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.