DPDK usage discussions
 help / color / mirror / Atom feed
From: 廖書華 <sim860927@gmail.com>
To: users@dpdk.org
Cc: 林庭安 <lingwanjae@gmail.com>
Subject: Primary with error : EAL: Failed to attach device on primary process
Date: Mon, 18 Oct 2021 15:35:16 +0800
Message-ID: <CANq=q40gZfAWJ8B0DqD5uteK__kc+KNOc4y9hi2+Kv0qw_33Tg@mail.gmail.com> (raw)

Dear,

My DPDK version is for 19.11 using x86_64-native-linuxapp-icc for the
compilation with VFIO module.

I bump into the error *EAL: Failed to attach device on primary process *while
running with my own application. This error is caused when calling function
plug() in function local_dev_probe(), currently the return value is -17,
not for expected 0. Can someone give me some suggestions ?
Here's the related DPDK log of my application.
xran_ethdi_init_dpdk_io: Calling rte_eal_init:wls_0 -c 0x2000021 -n2
--iova-mode=pa --socket-mem=8192 --socket-limit=8192 --proc-type=auto
--file-prefix wls_0 EAL: Detected 40 lcore(s) EAL: Detected 2 NUMA nodes
EAL: Auto-detected process type: PRIMARY EAL: Multi-process socket
/var/run/dpdk/wls_0/mp_socket EAL: Selected IOVA mode 'PA' EAL: Probing
VFIO support... EAL: VFIO support initialized EAL: PCI device 0000:01:00.0
on NUMA socket 0 EAL: probe driver: 8086:1539 net_e1000_igb EAL: PCI device
0000:02:00.0 on NUMA socket 0 EAL: probe driver: 8086:1539 net_e1000_igb
EAL: PCI device 0000:18:00.0 on NUMA socket 0 EAL: probe driver: 8086:1583
net_i40e EAL: PCI device 0000:18:00.1 on NUMA socket 0 EAL: probe driver:
8086:1583 net_i40e EAL: PCI device 0000:86:00.0 on NUMA socket 1 EAL: probe
driver: 8086:1572 net_i40e EAL: PCI device 0000:86:00.1 on NUMA socket 1
EAL: probe driver: 8086:1572 net_i40e EAL: PCI device 0000:86:00.2 on NUMA
socket 1 EAL: probe driver: 8086:1572 net_i40e EAL: PCI device 0000:86:00.3
on NUMA socket 1 EAL: probe driver: 8086:1572 net_i40e EAL: PCI device
0000:86:02.0 on NUMA socket 1 EAL: probe driver: 8086:154c net_i40e_vf EAL:
using IOMMU type 1 (Type 1) EAL: PCI device 0000:86:02.1 on NUMA socket 1
EAL: probe driver: 8086:154c net_i40e_vf Return value (int) of
rte_pdump_init() : 0 Return value of function rte_devargs_parse() : 0
Return value of function rte_devargs_insert() : 0 Return value of function
scan() : 0 EAL: PCI device 0000:86:02.0 on NUMA socket 1 Return value of
function plug() : -17 local_dev_probe : -17 EAL: Failed to attach device on
primary process initializing port 0 for TX, drv=net_i40e_vf Port 0 MAC: 00
11 22 33 44 66 Port 0: nb_rxd 4096 nb_txd 4096 Checking link status portid
[0] ... done Port 0 Link Up - speed 10000 Mbps - full-duplex Return value
of function rte_devargs_parse() : 0 Return value of function
rte_devargs_insert() : 0 Return value of function scan() : 0 EAL: PCI
device 0000:86:02.1 on NUMA socket 1 Return value of function plug() : -17
local_dev_probe : -17 EAL: Failed to attach device on primary process
initializing port 1 for TX, drv=net_i40e_vf Port 1 MAC: 00 11 22 33 44 66
Port 1: nb_rxd 4096 nb_txd 4096 Checking link status portid [1] ... done
Port 1 Link Up - speed 10000 Mbps - full-duplex vf 0 local SRC MAC: 00 11
22 33 44 66 vf 0 remote DST MAC: 00 11 22 33 44 55 vf 1 local SRC MAC: 00
11 22 33 44 66 vf 1 remote DST MAC: 00 11 22 33 44 55

P.S.1 : If I parse -w 0000:00:00.0 as the input of rte_eal_init()  in my
primary, the problem  *EAL: Failed to attach device on primary process*  will
*Disappear*, do someone has any idea about this ?

P.S.2 : If I parse the below device (-w 0000:86:02.0 -w 0000:86:02.1) as
the input of rte_eal_init() in my primary, it also bumps into the problem *EAL:
Failed to attach device on primary process.*
* - Log of binding DPDK port*

[oai@ee705-7-ip120 dpdk-19.11]$ ./usertools/dpdk-devbind.py --status

Network devices using DPDK-compatible driver
============================================
0000:86:02.0 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci
unused=iavf
0000:86:02.1 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci
unused=iavf


Can someone help me ?

Best Regards,
Shu-hua, Liao

                 reply	other threads:[~2021-10-18  7:35 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='CANq=q40gZfAWJ8B0DqD5uteK__kc+KNOc4y9hi2+Kv0qw_33Tg@mail.gmail.com' \
    --to=sim860927@gmail.com \
    --cc=lingwanjae@gmail.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 http://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/ http://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