DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Jesper Wramberg <jesper.wramberg@gmail.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] X520 virtual functions worked in 2.0 but fails in 2.1
Date: Wed, 16 Sep 2015 11:27:35 +0000	[thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6127F9D10@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CALhSPotpghptLbBL3rO-849-D5VMj_QcLB70H6xuQbgKSStbeQ@mail.gmail.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jesper Wramberg
> Hi all,

Hi Jesper,

> I got a Dell PowerEdge R630 with an X520 NIC. I want to set up two VFs that
> use the first port on the NIC. I've done the following:

Your process is correct - nothing wrong here.

> EAL: PCI device 0000:03:10.0 on NUMA socket 0
> EAL:   probe driver: 8086:10ed rte_ixgbevf_pmd
> EAL:   PCI memory mapped at 0x7f08c0108000
> EAL:   PCI memory mapped at 0x7f08c010c000
> PMD: eth_ixgbevf_dev_init():  >>
> PMD: ixgbevf_intr_disable():  >>
> PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -100
> PMD: rte_eth_dev_init: driver rte_ixgbevf_pmd:
> eth_dev_init(vendor_id=0x32902 device_id=0x10ed) failed
> EAL: Error - exiting with code: 1
>   Cause: Requested device 0000:03:10.0 cannot be used

This is a recently-discovered regression from commit
0eb609239efdb52a1cea5abca5e3316052071d81 in the ixgbe driver - a fix is in progress.

The code in the diff below[1] of the above commit is the offender,
And adding the code back in solves the immediate problem here.

If this temporary fix doesn't work, please let me know.
Cheers, -Harry

[1] Snipped of diff that breaks DPDK PF / VF mailbox handling:
 @@ -1000,12 +1038,6 @@ eth_ixgbe_dev_init(struct rte_eth_dev *eth_dev)
                         eth_dev->data->port_id, pci_dev->id.vendor_id,
                         pci_dev->id.device_id);
 
 -       rte_intr_callback_register(&(pci_dev->intr_handle),
 -               ixgbe_dev_interrupt_handler, (void *)eth_dev);
 -
 -       /* enable uio intr after callback register */
 -       rte_intr_enable(&(pci_dev->intr_handle));
 -
         /* enable support intr */
         ixgbe_enable_intr(eth_dev);

  reply	other threads:[~2015-09-16 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  9:58 Jesper Wramberg
2015-09-16 11:27 ` Van Haaren, Harry [this message]
2015-09-17  9:35   ` Jesper Wramberg

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=E923DB57A917B54B9182A2E928D00FA6127F9D10@IRSMSX102.ger.corp.intel.com \
    --to=harry.van.haaren@intel.com \
    --cc=dev@dpdk.org \
    --cc=jesper.wramberg@gmail.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).