DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Dirk-Holger Lenz <dirk.lenz@ng4t.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] i40e: Failed to init adminq
Date: Wed, 10 Jun 2015 11:50:48 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028604696DC9@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <55780D8C.40605@ng4t.com>

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 0000: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 0000: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 0x1800000 bytes
> EAL: Virtual area found at 0x7ff9a6000000 (size = 0x1800000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff9a5c00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x9800000 bytes
> EAL: Virtual area found at 0x7ff99c200000 (size = 0x9800000)
> EAL: Ask a virtual area of 0x7200000 bytes
> EAL: Virtual area found at 0x7ff994e00000 (size = 0x7200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff994a00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x57400000 bytes
> EAL: Virtual area found at 0x7ff93d400000 (size = 0x57400000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7ff93cc00000 (size = 0x600000)
> EAL: Ask a virtual area of 0x1a00000 bytes
> EAL: Virtual area found at 0x7ff93b000000 (size = 0x1a00000)
> EAL: Ask a virtual area of 0x6e00000 bytes
> EAL: Virtual area found at 0x7ff934000000 (size = 0x6e00000)
> EAL: Ask a virtual area of 0x7000000 bytes
> EAL: Virtual area found at 0x7ff92ce00000 (size = 0x7000000)
> EAL: Ask a virtual area of 0x5600000 bytes
> EAL: Virtual area found at 0x7ff927600000 (size = 0x5600000)
> EAL: Ask a virtual area of 0xc00000 bytes
> EAL: Virtual area found at 0x7ff926800000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff926400000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7ff925e00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff925a00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x7c800000 bytes
> EAL: Virtual area found at 0x7ff8a9000000 (size = 0x7c800000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff8a8c00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff8a8800000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7ff8a8200000 (size = 0x400000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7ff8a7a00000 (size = 0x600000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff8a7600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff8a7200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7ff8a6c00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7ff8a6200000 (size = 0x800000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7ff8a5c00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7ff8a5600000 (size = 0x400000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7ff8a4400000 (size = 0x1000000)
> EAL: Requesting 1024 pages of size 2MB from socket 0
> EAL: Requesting 1024 pages of size 2MB from socket 1
> EAL: TSC frequency is ~2599997 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 0000: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 0000:01:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:01:00.2 on NUMA socket 0
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:01:00.3 on NUMA socket 0
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:03:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
> EAL:   PCI memory mapped at 0x7ff9a7800000
> EAL:   PCI memory mapped at 0x7ff9a7880000
> PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 12, SFP+: 3
> PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x10fb
> EAL: PCI device 0000:03:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
> EAL:   PCI memory mapped at 0x7ff9a7884000
> EAL:   PCI memory mapped at 0x7ff9a7904000
> PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 12, SFP+: 4
> PMD: eth_ixgbe_dev_init(): port 1 vendorID=0x8086 deviceID=0x10fb
> EAL: PCI device 0000: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 0000:82:00.0 cannot be used
>
> Best regards
> Dirk
>
>
>


      reply	other threads:[~2015-06-10 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 10:12 Dirk-Holger Lenz
2015-06-10 11:50 ` Qiu, Michael [this message]

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=533710CFB86FA344BFBF2D6802E6028604696DC9@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=dev@dpdk.org \
    --cc=dirk.lenz@ng4t.com \
    /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).