DPDK usage discussions
 help / color / mirror / Atom feed
From: CHANWEN.LIAO 廖展文 <CHANWEN.LIAO@deltaww.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Cannot attach NIC to my application
Date: Mon, 7 Sep 2020 08:49:13 +0000
Message-ID: <HK2PR01MB3348F1881CD8436D7E4338F190280@HK2PR01MB3348.apcprd01.prod.exchangelabs.com> (raw)

Hi,

I’m trying to attach NIC to my application using dpdk-stable-17.11.5, but rte_eth_dev_attach() return -1.
Could you help me to clarify why this happened?

Network devices using DPDK-compatible driver
======================================
0000:12:00.1 ‘FastLinQ QL41000 Series 10/25/40/50GbE Controller 8070’ drv=igb_uio unused=qede

Fail print:
EAL: Detected 40 lcore(s)
EAL: Auto-detected process type: PRIMARY
EAL: Probing VFIO support…
EAL: PCI device 0000:12:00.0 on NUMA socket 0
EAL:  probe driver: 1077:8070 net_qede
EAL: PCI device 0000:12:00.1 on NUMA socket 0
EAL:  probe driver: 1077:8070 net_qede
[QEDE PMD:  ()]ecore_spq_block:Ramrod is stuck [CID ff100000 cmd 01 proto 08 echo 0000]
[qede_hw_err_notify:297()] HW error occurred [Ramrod Failure]
[QEDE PMD:  ()]ecore_hw_init_pf:Function start ramrod failed
[QEDE PMD:  ()]ecore_hw_init:init phase failed for loadcode 0x10100000 (rc -2)
[qed_slowpath_start:295(12:00.1:dpdk-port-0)]ecore_hw_init failed
[qede_common_dev_init:2975(12:00.1:dpdk-port-0)]Cannot start slowpath rc = -2
EAL: Requested device 0000:12:00.1 cannot be used

*************************************************************************
This email message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message. [Delta Electronics, INC. Taiwan]
*************************************************************************

                 reply	other threads:[~2020-09-07  8:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=HK2PR01MB3348F1881CD8436D7E4338F190280@HK2PR01MB3348.apcprd01.prod.exchangelabs.com \
    --to=chanwen.liao@deltaww.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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git