DPDK patches and discussions
 help / color / mirror / Atom feed
From: Emerson Posadas <toxickore@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Failed to initialize HW 0x10bc
Date: Fri, 03 Jul 2015 14:59:15 +0000	[thread overview]
Message-ID: <CAD_Vvh_+CE9qD27Fk2nKB2r4tSL3P_C1M6Xn351UNobANrk-PA@mail.gmail.com> (raw)

Hello

I´m trying to use the pktgen tool to generate some traffic, but my
device (Intel
Corporation 82571EB Gigabit Ethernet) is failing to initialize. Is this
related with the resolved issue 7.19, even when is not the same device?

http://dpdk.org/doc/guides/rel_notes/resolved_issues.html

Here is my output while running pktgen:
PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x10bc: failed
to init HW
EAL: Error - exiting with code: 1
  Cause: Requested device 0000:03:00.0 cannot be used

And
>From lib/librte_eal/common/include/rte_pci_dev_ids.h
#define E1000_DEV_ID_82571EB_QUAD_COPPER_LP   0x10BC

[root@localhost dpdk-2.0.0]# dpdk_nic_bind.py --status

Network devices using DPDK-compatible driver
============================================
0000:03:00.0 '82571EB Gigabit Ethernet Controller (Copper)' drv=igb_uio
unused=
0000:03:00.1 '82571EB Gigabit Ethernet Controller (Copper)' drv=igb_uio
unused=
0000:04:00.0 '82571EB Gigabit Ethernet Controller (Copper)' drv=igb_uio
unused=
0000:04:00.1 '82571EB Gigabit Ethernet Controller (Copper)' drv=igb_uio
unused=

Network devices using kernel driver
===================================
0000:00:19.0 '82579LM Gigabit Network Connection' if=eno1 drv=e1000e
unused=igb_uio *Active*

Any advice would be useful.

EP

             reply	other threads:[~2015-07-03 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 14:59 Emerson Posadas [this message]
2015-07-03 15:09 ` Bruce Richardson
2015-07-03 16:45 Posadas, Emerson
2015-07-03 21:19 Posadas, Emerson

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=CAD_Vvh_+CE9qD27Fk2nKB2r4tSL3P_C1M6Xn351UNobANrk-PA@mail.gmail.com \
    --to=toxickore@gmail.com \
    --cc=dev@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).