From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla@dpdk.org Subject: [Bug 86] Requested device cannot be used Date: Tue, 28 Aug 2018 02:18:35 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable To: dev@dpdk.org Return-path: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D86 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/R= 730, 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 ei= ther igb_uio or vfio_pci: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Network devices using DPDK-compatible driver =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 0000:82:00.0 'Ethernet 10G 2P X520 Adapter 154d' drv=3Digb_uio unused=3Dvfi= o-pci 0000:82:00.1 'Ethernet 10G 2P X520 Adapter 154d' drv=3Digb_uio unused=3Dvfi= o-pci Network devices using kernel driver =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 0000:01:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=3Deno1 drv= =3Dtg3 unused=3Digb_uio,vfio-pci=20 0000:01:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=3Deno2 drv= =3Dtg3 unused=3Digb_uio,vfio-pci=20 0000:02:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=3Deno3 drv= =3Dtg3 unused=3Digb_uio,vfio-pci=20 0000:02:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=3Deno4 drv= =3Dtg3 unused=3Digb_uio,vfio-pci *Active* Other Network devices =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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-vswi= tch, 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 =20=20 2018-08-27T09:54:05.548Z|00005|reconnect|INFO|unix:/usr/local/var/run/openv= switch/db.sock: connecting... 2018-08-=20=20 27T09:54:05.549Z|00006|reconnect|INFO|unix:/usr/local/var/run/openvswitch/d= b.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: Data= path 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 NU= MA 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 configurati= on (Invalid argument) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I've tried a solution described in https://goo.gl/3opVRT, which is utilizi= ng "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. --=20 You are receiving this mail because: You are the assignee for the bug.=