From: Sunghyuk Kay <sunghyuk.kay@kaist.ac.kr>
To: users@dpdk.org
Subject: [dpdk-users] "eth_i40e_dev_init(): Failed to init adminq: -66" problem
Date: Fri, 10 Apr 2020 17:29:47 +0900 [thread overview]
Message-ID: <CAGsexd7=1VROy7Bwcd0o3uJqj-D6ntHbgjpuc_o_7_nTs1w-UQ@mail.gmail.com> (raw)
Hi all,
I'm setting DPDK on our hardware to do some experiment, but suffering from .
I was trying to use DPDK on Ubuntu 18.04 with Intel XL710 Ethernet Adapter
with igb_uio driver. I've compiled DPDK from source, and bound the driver
to NIC.
But when I run `testpmd` application, it returns an error like this.
```
$ sudo ./build/app/testpmd
EAL: Detected 128 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:81:00.0 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
eth_i40e_dev_init(): Failed to init adminq: -66
EAL: ethdev initialisation failedEAL: Requested device 0000:81:00.0 cannot
be used
EAL: PCI device 0000:81:00.1 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
eth_i40e_dev_init(): Failed to init adminq: -66
EAL: ethdev initialisation failedEAL: Requested device 0000:81:00.1 cannot
be used
EAL: PCI device 0000:c4:00.0 on NUMA socket 0
EAL: probe driver: 8086:1533 net_e1000_igb
EAL: PCI device 0000:c5:00.0 on NUMA socket 0
EAL: probe driver: 8086:1533 net_e1000_igb
testpmd: No probed ethernet devices
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=1163456, size=2176,
socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done
No commandline core given, start packet forwarding
io packet forwarding - ports=0 - cores=0 - streams=0 - NUMA support
enabled, MP allocation mode: native
io packet forwarding packets/burst=32
nb forwarding cores=1 - nb forwarding ports=0
Press enter to exit
Telling cores to stop...
Waiting for lcores to finish...
+++++++++++++++ Accumulated forward statistics for all
ports+++++++++++++++
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 0 TX-dropped: 0 TX-total: 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Done.
Bye...
```
I tried to find what return code -66 from adminq means, but I couldn't find
it.
Some say this might have to do with Intel IOMMU pass-through, but I'm not
sure that's the case.
Has anyone had this issue before? Maybe some tip on this issue would be
very helpful.
Thank you,
Sunghyuk
next reply other threads:[~2020-04-10 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 8:29 Sunghyuk Kay [this message]
[not found] ` <CAJyVW49LOPQiVnorQ4=YECjDu4zfAci_7JmQx27hdA=TV9a2wQ@mail.gmail.com>
2020-04-10 13:31 ` Sunghyuk Kay
2020-04-10 14:29 ` Dheeraj Dang
2020-04-16 4:00 ` Sunghyuk Kay
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='CAGsexd7=1VROy7Bwcd0o3uJqj-D6ntHbgjpuc_o_7_nTs1w-UQ@mail.gmail.com' \
--to=sunghyuk.kay@kaist.ac.kr \
--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).