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

Hey there,

Thanks for your help. I checked the eth_ixgbevf_dev_init() function against
DPDK 2.0 but did think about changes in the eth_ixgbe_dev_init() function.
Anyway, I have just been using 2.0 for now but it's nice to know I wasn't
doing anything wrong :-)

Regards,
Jesper Wramberg

2015-09-16 13:27 GMT+02:00 Van Haaren, Harry <harry.van.haaren@intel.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-17  9:35 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
2015-09-17  9:35   ` Jesper Wramberg [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='CALhSPov0Mu0baxU=ruJQ6E5_wu4mq6di99GBRzBzUXUQAoYRHA@mail.gmail.com' \
    --to=jesper.wramberg@gmail.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@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).