From: ".." <hyperhead@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Intel XVV710- i40e dpdk-devbind error "Set default VSI failed, err I40E_ERR_ADMIN_QUEUE_ERROR"
Date: Thu, 4 Oct 2018 18:33:44 +0200 [thread overview]
Message-ID: <CAL0gemO45rB2aNzkU3Q4Oo9esm1761KfY-DzYnn3MjQ0kUn2UQ@mail.gmail.com> (raw)
In-Reply-To: <20181004082336.24ada719@xeon-e3>
Hi,
I solved it by loading the igb_uio drivers and using that instead. I read
igb_uio is used on those model of cards in the dpdk documentation, lesson
learned.
Thanks for the response.
Roland
On Thu, 4 Oct 2018, 17:23 Stephen Hemminger, <stephen@networkplumber.org>
wrote:
> On Thu, 4 Oct 2018 11:17:53 +0200
> ".." <hyperhead@gmail.com> wrote:
>
> > Hi dpdk-users!
> >
> > I have some new 25G cards:
> > Intel Corporation Ethernet Network Adapter XXV710-2
> >
> > I am using the latest i40e driver
> >
> > filename:
> >
> /lib/modules/3.10.0-862.11.6.el7.x86_64/updates/drivers/net/ethernet/intel/i40e/i40e.ko
> > version: 2.4.10
> > license: GPL
> > description: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver
> > author: Intel Corporation, <e1000-devel@lists.sourceforge.net>
> > retpoline: Y
> >
> > When I try to do dpdk-devbind I get the following error
> >
> > Error: bind failed for 0000:05:00.0 - Cannot bind to driver
> uio_pci_generic
> >
> > This shows in dmesg
> > [240097.901062] i40e 0000:05:00.1: removed PHC from ens2f1
> > [240097.966118] i40e 0000:05:00.1: Set default VSI failed, err
> > I40E_ERR_ADMIN_QUEUE_ERROR, aq_err I40E_AQ_RC_EINVAL
> > [240097.966122] i40e 0000:05:00.1: Setting promiscuous on failed on PF,
> err
> > I40E_ERR_ADMIN_QUEUE_ERROR aq_err I40E_AQ_RC_EINVAL
> >
> > I am moving from some much older 1G cards I had, but they were binding
> ok,
> > however it was the igb driver.
> >
> > I can seem to find much, I guess these are quite new cards and the driver
> > is up to date as well, a bug maybe?
> >
> > Thanks
> >
> > Roland
>
> Make sure you update the firmware on the Intel card before doing anything
> else.
> Also you should use VFIO if at all possible.
>
prev parent reply other threads:[~2018-10-04 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 9:17 ..
2018-10-04 15:23 ` Stephen Hemminger
2018-10-04 16:33 ` .. [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=CAL0gemO45rB2aNzkU3Q4Oo9esm1761KfY-DzYnn3MjQ0kUn2UQ@mail.gmail.com \
--to=hyperhead@gmail.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
/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).