From: Stephen Hemminger <stephen@networkplumber.org>
To: "Weglicki, MichalX" <michalx.weglicki@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problem with using VF: Initialization Failure: -15
Date: Wed, 11 Apr 2018 07:12:31 -0700 [thread overview]
Message-ID: <20180411071231.6d61fce1@xeon-e3> (raw)
In-Reply-To: <1AFA2937E172CD4DB2FD9318443C060E40DB9C32@IRSMSX102.ger.corp.intel.com>
On Wed, 11 Apr 2018 12:01:09 +0000
"Weglicki, MichalX" <michalx.weglicki@intel.com> wrote:
> Hello,
>
> I'm trying to test very simple scenario, creating two VFs and testing it with test-pmd. Unfortunately I can't make it to work
> DPDK Version: v17.11 (I've checked also 18.02)
> NIC: Niantic 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
> Kernel: 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> Steps:
> Creating two VFs. Binding each VF to a driver (I also tried vfio_pci with same results):
> ../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.0
> ../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.1
>
> ./testpmd -c 0x3 -n 4 --socket-mem 512 -- --burst=64 -i --txqflags=0xf00 --disable-hw-vlan
> EAL: Detected 56 lcore(s)
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:03:00.3 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:05:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:05:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:10.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10ed net_ixgbe_vf
> PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> EAL: Requested device 0000:81:10.0 cannot be used
> EAL: PCI device 0000:81:10.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10ed net_ixgbe_vf
> PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> EAL: Requested device 0000:81:10.1 cannot be used
> EAL: PCI device 0000:83:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:83:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: No probed ethernet devices
> Interactive-mode selected
>
> I've investigated the issue, and the problem is with:
> diag = hw->mac.ops.reset_hw(hw);
> which calls:
> e1000_reset_hw_vf
> and it calls:
> e1000_read_posted_mbx
> Which returns: E1000_ERR_MBX (-15)
>
> Is this common issue, or some configuration problem?
>
> Thank you all in advance.
>
> Br,
> Michal.
What host? It could be that ixgbevf communication (over mailbox) is not supported
by the older PF driver on the host.
next prev parent reply other threads:[~2018-04-11 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 12:01 Weglicki, MichalX
2018-04-11 14:12 ` Stephen Hemminger [this message]
2018-04-13 7:03 ` Rosen, Rami
2018-04-16 6:35 ` Weglicki, MichalX
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=20180411071231.6d61fce1@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=michalx.weglicki@intel.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).