[dpdk-dev] [i40e] Failed to init adminq?
Hi, I'm having an issue with the i40e pmd failing to initialise a port. I've tried powercycling with the linux i40e driver removed and blacklisted as suggested here: http://dpdk.org/ml/archives/dev/2015-June/019132.html, but it's still persisting. It used to initialise without issues so I'm not sure what could have changed? I'm running it in the host at the moment but I have used that port pci passthrough'd to a guest also. Any suggestions as to what could be causing this? Thanks, Eimear EAL: PCI device :86:00.0 on NUMA socket 1 EAL: probe driver: 8086:1572 rte_i40e_pmd EAL: PCI memory mapped at 0x7f5d4000 EAL: PCI memory mapped at 0x7f5d4080 PMD: eth_i40e_dev_init(): Failed to init adminq: -54 EAL: Error - exiting with code: 1 Cause: Requested device :86:00.0 cannot be used
[dpdk-dev] [i40e] Failed to init adminq?
On Fri, 4 Dec 2015 11:25:09 + "Eimear Morrissey" wrote: > > > Hi, > > I'm having an issue with the i40e pmd failing to initialise a port. I've > tried powercycling with the linux i40e driver removed and blacklisted as > suggested here: http://dpdk.org/ml/archives/dev/2015-June/019132.html, but > it's still persisting. It used to initialise without issues so I'm not sure > what could have changed? I'm running it in the host at the moment but I > have used that port pci passthrough'd to a guest also. > > Any suggestions as to what could be causing this? > > Thanks, > Eimear > > EAL: PCI device :86:00.0 on NUMA socket 1 > EAL: probe driver: 8086:1572 rte_i40e_pmd > EAL: PCI memory mapped at 0x7f5d4000 > EAL: PCI memory mapped at 0x7f5d4080 > PMD: eth_i40e_dev_init(): Failed to init adminq: -54 > EAL: Error - exiting with code: 1 > Cause: Requested device :86:00.0 cannot be used For me, it turned out to be a bug in earlier version of a patch to support xen dom0. This happens if the memory zone setup in i40e_allocate_dma_mem_d was not providing correct addresses. Anyway check if you have that correct. Also, updating firmware took more effort than expected. 1. Need to run Intel's out of tree Linux driver for i40e or the version in 4.4-rc1 or later. 2. Need to use Linux driver (ie no DPDK) 3. System needs access to internet to download firmware Overall, it is one of those "pray for bits" updates.
[dpdk-dev] [i40e] Failed to init adminq?
Stephen Hemminger wrote on 12/04/2015 05:36:08 PM: > From: Stephen Hemminger > To: Eimear Morrissey/Ireland/IBM at IBMIE > Cc: dev at dpdk.org > Date: 12/04/2015 05:36 PM > Subject: Re: [dpdk-dev] [i40e] Failed to init adminq? > > On Fri, 4 Dec 2015 11:25:09 + > "Eimear Morrissey" wrote: > > > > > > > Hi, > > > > I'm having an issue with the i40e pmd failing to initialise a port. I've > > tried powercycling with the linux i40e driver removed and blacklisted as > > suggested here: http://dpdk.org/ml/archives/dev/2015-June/019132.html, but > > it's still persisting. It used to initialise without issues so I'm not sure > > what could have changed? I'm running it in the host at the moment but I > > have used that port pci passthrough'd to a guest also. > > > > Any suggestions as to what could be causing this? > > > > Thanks, > > Eimear > > > > EAL: PCI device :86:00.0 on NUMA socket 1 > > EAL: probe driver: 8086:1572 rte_i40e_pmd > > EAL: PCI memory mapped at 0x7f5d4000 > > EAL: PCI memory mapped at 0x7f5d4080 > > PMD: eth_i40e_dev_init(): Failed to init adminq: -54 > > EAL: Error - exiting with code: 1 > > Cause: Requested device :86:00.0 cannot be used > > > For me, it turned out to be a bug in earlier version > of a patch to support xen dom0. This happens if the memory zone > setup in i40e_allocate_dma_mem_d was not providing correct addresses. > > Anyway check if you have that correct. > > Also, updating firmware took more effort than expected. > 1. Need to run Intel's out of tree Linux driver for i40e > or the version in 4.4-rc1 or later. > 2. Need to use Linux driver (ie no DPDK) > 3. System needs access to internet to download firmware > > Overall, it is one of those "pray for bits" updates. > I'm using DPDK 2.1.0 - I'm not sure if that has the correct patch version or not? What's confusing is that it used to work but now it's completely stopped working & nothing (powercycling, binding to different drivers and back, even replacing the actual card) seems to affect it. I haven't upgraded the firmware on the card, but will try. -Eimear
[dpdk-dev] i40e: Failed to init adminq
Hello, since I updated from 2.0.0 released to the current git clone the i40e doesn't 'init' anymore. EAL: PCI device :82:00.0 on NUMA socket 1 EAL: probe driver: 8086:1572 rte_i40e_pmd EAL: PCI memory mapped at 0x7ff8a23fd000 EAL: PCI memory mapped at 0x7ff9ae2ec000 PMD: eth_i40e_dev_init(): Failed to init adminq: -54 EAL: Error - exiting with code: 1 Cause: Requested device :82:00.0 cannot be used It's plain hardware no virtual machine, I'm using kernel: 3.16.0-29-lowlatency on Ubuntu 14.04. This occurs already in the rte_eal_init() function call. Beside this the ixgbe with 82599 comes up and works (when I disable the i40e). Here the complete log: sudo ./build/helloworld -c 0xf -n 3 EAL: Detected lcore 0 as core 0 on socket 0 EAL: Detected lcore 1 as core 0 on socket 1 EAL: Detected lcore 2 as core 1 on socket 0 EAL: Detected lcore 3 as core 1 on socket 1 EAL: Detected lcore 4 as core 2 on socket 0 EAL: Detected lcore 5 as core 2 on socket 1 EAL: Detected lcore 6 as core 3 on socket 0 EAL: Detected lcore 7 as core 3 on socket 1 EAL: Detected lcore 8 as core 4 on socket 0 EAL: Detected lcore 9 as core 4 on socket 1 EAL: Detected lcore 10 as core 5 on socket 0 EAL: Detected lcore 11 as core 5 on socket 1 EAL: Detected lcore 12 as core 6 on socket 0 EAL: Detected lcore 13 as core 6 on socket 1 EAL: Detected lcore 14 as core 7 on socket 0 EAL: Detected lcore 15 as core 7 on socket 1 EAL: Support maximum 128 logical core(s) by configuration. EAL: Detected 16 lcore(s) EAL: VFIO modules not all loaded, skip VFIO support... EAL: Setting up memory... EAL: Ask a virtual area of 0x180 bytes EAL: Virtual area found at 0x7ff9a600 (size = 0x180) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff9a5c0 (size = 0x20) EAL: Ask a virtual area of 0x980 bytes EAL: Virtual area found at 0x7ff99c20 (size = 0x980) EAL: Ask a virtual area of 0x720 bytes EAL: Virtual area found at 0x7ff994e0 (size = 0x720) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff994a0 (size = 0x20) EAL: Ask a virtual area of 0x5740 bytes EAL: Virtual area found at 0x7ff93d40 (size = 0x5740) EAL: Ask a virtual area of 0x60 bytes EAL: Virtual area found at 0x7ff93cc0 (size = 0x60) EAL: Ask a virtual area of 0x1a0 bytes EAL: Virtual area found at 0x7ff93b00 (size = 0x1a0) EAL: Ask a virtual area of 0x6e0 bytes EAL: Virtual area found at 0x7ff93400 (size = 0x6e0) EAL: Ask a virtual area of 0x700 bytes EAL: Virtual area found at 0x7ff92ce0 (size = 0x700) EAL: Ask a virtual area of 0x560 bytes EAL: Virtual area found at 0x7ff92760 (size = 0x560) EAL: Ask a virtual area of 0xc0 bytes EAL: Virtual area found at 0x7ff92680 (size = 0xc0) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff92640 (size = 0x20) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7ff925e0 (size = 0x40) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff925a0 (size = 0x20) EAL: Ask a virtual area of 0x7c80 bytes EAL: Virtual area found at 0x7ff8a900 (size = 0x7c80) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff8a8c0 (size = 0x20) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff8a880 (size = 0x20) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7ff8a820 (size = 0x40) EAL: Ask a virtual area of 0x60 bytes EAL: Virtual area found at 0x7ff8a7a0 (size = 0x60) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff8a760 (size = 0x20) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7ff8a720 (size = 0x20) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7ff8a6c0 (size = 0x40) EAL: Ask a virtual area of 0x80 bytes EAL: Virtual area found at 0x7ff8a620 (size = 0x80) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7ff8a5c0 (size = 0x40) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7ff8a560 (size = 0x40) EAL: Ask a virtual area of 0x100 bytes EAL: Virtual area found at 0x7ff8a440 (size = 0x100) EAL: Requesting 1024 pages of size 2MB from socket 0 EAL: Requesting 1024 pages of size 2MB from socket 1 EAL: TSC frequency is ~257 KHz EAL: Master lcore 0 is ready (tid=ae32a900;cpuset=[0]) EAL: lcore 2 is ready (tid=a3bfe700;cpuset=[2]) EAL: lcore 3 is ready (tid=a33fd700;cpuset=[3]) EAL: lcore 1 is ready (tid=a43ff700;cpuset=[1]) EAL: PCI device :01:00.0 on NUMA socket 0 EAL: probe driver: 8086:1521 rte_igb_pmd EAL: Not managed by a supported kernel driver, skipped EAL: PCI device :01:00.1 on NUMA socket 0 EAL: probe driver: 8086:1521 rte_igb_pmd EAL: Not managed by a supported ke
[dpdk-dev] i40e: Failed to init adminq
Hi, This is an know issue, as I faced before. One workaround: remove i40e kernel driver, power off server, then power on. After that start dpdk, it should work. Thanks, Michael On 6/10/2015 6:12 PM, Dirk-Holger Lenz wrote: > Hello, > since I updated from 2.0.0 released to the current git clone the i40e > doesn't 'init' anymore. >EAL: PCI device :82:00.0 on NUMA socket 1 >EAL: probe driver: 8086:1572 rte_i40e_pmd >EAL: PCI memory mapped at 0x7ff8a23fd000 >EAL: PCI memory mapped at 0x7ff9ae2ec000 >PMD: eth_i40e_dev_init(): Failed to init adminq: -54 >EAL: Error - exiting with code: 1 > Cause: Requested device :82:00.0 cannot be used > It's plain hardware no virtual machine, I'm using kernel: > 3.16.0-29-lowlatency > on Ubuntu 14.04. > This occurs already in the rte_eal_init() function call. > Beside this the ixgbe with 82599 comes up and works (when I disable the > i40e). > > Here the complete log: > sudo ./build/helloworld -c 0xf -n 3 > EAL: Detected lcore 0 as core 0 on socket 0 > EAL: Detected lcore 1 as core 0 on socket 1 > EAL: Detected lcore 2 as core 1 on socket 0 > EAL: Detected lcore 3 as core 1 on socket 1 > EAL: Detected lcore 4 as core 2 on socket 0 > EAL: Detected lcore 5 as core 2 on socket 1 > EAL: Detected lcore 6 as core 3 on socket 0 > EAL: Detected lcore 7 as core 3 on socket 1 > EAL: Detected lcore 8 as core 4 on socket 0 > EAL: Detected lcore 9 as core 4 on socket 1 > EAL: Detected lcore 10 as core 5 on socket 0 > EAL: Detected lcore 11 as core 5 on socket 1 > EAL: Detected lcore 12 as core 6 on socket 0 > EAL: Detected lcore 13 as core 6 on socket 1 > EAL: Detected lcore 14 as core 7 on socket 0 > EAL: Detected lcore 15 as core 7 on socket 1 > EAL: Support maximum 128 logical core(s) by configuration. > EAL: Detected 16 lcore(s) > EAL: VFIO modules not all loaded, skip VFIO support... > EAL: Setting up memory... > EAL: Ask a virtual area of 0x180 bytes > EAL: Virtual area found at 0x7ff9a600 (size = 0x180) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff9a5c0 (size = 0x20) > EAL: Ask a virtual area of 0x980 bytes > EAL: Virtual area found at 0x7ff99c20 (size = 0x980) > EAL: Ask a virtual area of 0x720 bytes > EAL: Virtual area found at 0x7ff994e0 (size = 0x720) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff994a0 (size = 0x20) > EAL: Ask a virtual area of 0x5740 bytes > EAL: Virtual area found at 0x7ff93d40 (size = 0x5740) > EAL: Ask a virtual area of 0x60 bytes > EAL: Virtual area found at 0x7ff93cc0 (size = 0x60) > EAL: Ask a virtual area of 0x1a0 bytes > EAL: Virtual area found at 0x7ff93b00 (size = 0x1a0) > EAL: Ask a virtual area of 0x6e0 bytes > EAL: Virtual area found at 0x7ff93400 (size = 0x6e0) > EAL: Ask a virtual area of 0x700 bytes > EAL: Virtual area found at 0x7ff92ce0 (size = 0x700) > EAL: Ask a virtual area of 0x560 bytes > EAL: Virtual area found at 0x7ff92760 (size = 0x560) > EAL: Ask a virtual area of 0xc0 bytes > EAL: Virtual area found at 0x7ff92680 (size = 0xc0) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff92640 (size = 0x20) > EAL: Ask a virtual area of 0x40 bytes > EAL: Virtual area found at 0x7ff925e0 (size = 0x40) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff925a0 (size = 0x20) > EAL: Ask a virtual area of 0x7c80 bytes > EAL: Virtual area found at 0x7ff8a900 (size = 0x7c80) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff8a8c0 (size = 0x20) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff8a880 (size = 0x20) > EAL: Ask a virtual area of 0x40 bytes > EAL: Virtual area found at 0x7ff8a820 (size = 0x40) > EAL: Ask a virtual area of 0x60 bytes > EAL: Virtual area found at 0x7ff8a7a0 (size = 0x60) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff8a760 (size = 0x20) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7ff8a720 (size = 0x20) > EAL: Ask a virtual area of 0x40 bytes > EAL: Virtual area found at 0x7ff8a6c0 (size = 0x40) > EAL: Ask a virtual area of 0x80 bytes > EAL: Virtual area found at 0x7ff8a620 (size = 0x80) > EAL: Ask a virtual area of 0x40 bytes > EAL: Virtual area found at 0x7ff8a5c0 (size = 0x40) > EAL: Ask a virtual area of 0x40 bytes > EAL: Virtual area found at 0x7ff8a560 (size = 0x40) > EAL: Ask a virtual area of 0x100 bytes > EAL: Virtual area found at 0x7ff8a440 (size = 0x100) > EAL: Requesting 1024 pages of size 2MB from socket 0 > EAL: Requesting 1024 pages of size 2MB from socket 1 > EAL: TSC frequency is ~257 KHz > EAL: Master lcore 0 is ready (tid=ae32a900;cpuset=
