DPDK patches and discussions
 help / color / mirror / Atom feed
From: Saurabh Mishra <saurabh.globe@gmail.com>
To: "Qiu, Michael" <michael.qiu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-dev] i40evf DPDK init_adminq failed: -53
Date: Mon, 1 Feb 2016 10:25:00 -0800	[thread overview]
Message-ID: <CAMnwyJ2Cc+m=Yy3QHc-WPEmwdrcwSGHxgkWdb+jZec13vOZyMQ@mail.gmail.com> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E6028622F2812B@SHSMSX101.ccr.corp.intel.com>

Hi Michael --

What are the steps to upgrade i40e firmware. We are using CentOS7

It didn't work with guest VF driver either on ESXi and KVM.

Sure. I will blacklist i40evf driver and try it out.

Thanks,
/Saurabh


On Mon, Feb 1, 2016 at 12:16 AM, Qiu, Michael <michael.qiu@intel.com> wrote:

> Hi, Saurabh
>
> It's known issue, to fix this you'd better to upgrade the firmware
> version of i40e.
>
> BTW, will it work in guest with kernel driver?
>
> If yes, to workaround(somebody reports it does not work for them):
> Remove i40e.ko in guest, so that it will not auto-loaded when boot up.
>
> Hope it works for you.
>
> Thanks,
> Michael
>
>
> On 1/30/2016 4:35 AM, Saurabh Mishra wrote:
> > Has anybody seen this before? What's the workaround or fix? We are using
> > dpdk-2.2.0 on KVM centos:
> >
> > Host PF version: 1.0.11-k on Centos7
> >
> >
> > [root@ ~]# ./symmetric_mp fakeelf -c 2 -m2048 -n4 --proc-type=primary
> -- -p
> > 3 --num-procs=2 --proc-id=0
> >
> > [.]
> >
> > EAL: Virtual area found at 0x7fff75800000 (size = 0x200000)
> >
> > EAL: Requesting 1024 pages of size 2MB from socket 0
> >
> > EAL: TSC frequency is ~2600141 KHz
> >
> > EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using
> unreliable
> > clock cycles !
> >
> > EAL: Master lcore 1 is ready (tid=f7fed880;cpuset=[1])
> >
> > EAL: PCI device 0000:00:04.0 on NUMA socket 0
> >
> > EAL:   probe driver: 8086:154c rte_i40evf_pmd
> >
> > EAL:   PCI memory mapped at 0x7ffff6200000
> >
> > EAL:   PCI memory mapped at 0x7ffff6210000
> >
> > EAL: PCI device 0000:00:05.0 on NUMA socket 0
> >
> > EAL:   probe driver: 8086:154c rte_i40evf_pmd
> >
> > EAL:   PCI memory mapped at 0x7ffff6214000
> >
> > EAL:   PCI memory mapped at 0x7ffff6224000
> >
> > PMD: i40evf_init_vf(): init_adminq failed: -53
> >
> > PMD: i40evf_dev_init(): Init vf failed
> >
> > EAL: Error - exiting with code: 1
> >
> >   Cause: Requested device 0000:00:05.0 cannot be used
> >
> > [root@PA-VM ~]# ./dpdk-2.2.0/tools/dpdk_nic_bind.py --status
> >
> >
> > Network devices using DPDK-compatible driver
> >
> > ============================================
> >
> > 0000:00:04.0 'Device 154c' drv=igb_uio unused=uio_pci_generic
> >
> > 0000:00:05.0 'Device 154c' drv=igb_uio unused=uio_pci_generic
> >
> >
> > Network devices using kernel driver
> >
> > ===================================
> >
> > 0000:00:03.0 'RTL-8139/8139C/8139C+' if=eth0 drv=8139cp
> > unused=igb_uio,uio_pci_generic *Active*
> >
> >
> > Other network devices
> >
> > =====================
> >
> > <none>
> >
> > [root@ ~]#
> >
> >
> >
> > 04:00.0 *Ether*net controller: Intel Corporation *Ether*net Controller
> X710
> > for 10GbE SFP+ (rev 01)
> >
> > 04:00.1 *Ether*net controller: Intel Corporation *Ether*net Controller
> X710
> > for 10GbE SFP+ (rev 01)
> >
> > 04:02.0 *Ether*net controller: Intel Corporation XL710/X710 Virtual
> > Function (rev 01)
> >
> > 04:02.1 *Ether*net controller: Intel Corporation XL710/X710 Virtual
> > Function (rev 01)
> >
> > 04:0a.0 *Ether*net controller: Intel Corporation XL710/X710 Virtual
> > Function (rev 01)
> >
> > 04:0a.1 *Ether*net controller: Intel Corporation XL710/X710 Virtual
> > Function (rev 01)
> >
> >
> >
> > [root@oscompute3 ~]# dmesg | tail
> >
> > [2064188.042835] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.062836] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.082862] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.102838] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.122850] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.142852] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.162850] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.182845] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.202845] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [2064188.222858] i40evf 0000:04:0a.1: i40evf_add_ether_addrs: command 15
> > pending
> >
> > [root@oscompute3 ~]#
> >
> >
> > /Saurabh
> >
>
>

  reply	other threads:[~2016-02-01 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 20:34 Saurabh Mishra
2016-02-01  8:16 ` Qiu, Michael
2016-02-01 18:25   ` Saurabh Mishra [this message]
2016-02-01 19:49     ` Saurabh Mishra
2016-02-01 22:44       ` Saurabh Mishra
2016-02-02  3:00         ` Qiu, Michael
2016-02-02  2:36     ` Zhang, Helin

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='CAMnwyJ2Cc+m=Yy3QHc-WPEmwdrcwSGHxgkWdb+jZec13vOZyMQ@mail.gmail.com' \
    --to=saurabh.globe@gmail.com \
    --cc=dev@dpdk.org \
    --cc=michael.qiu@intel.com \
    --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).