From: "Rosen, Rami" <rami.rosen@intel.com>
To: Chris Hall <chris.hall@stackpath.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] l3fwd rte_eth_rx_queue_setup: err=-22
Date: Thu, 9 Feb 2017 05:22:39 +0000 [thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F93D4A3AFF@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <BN6PR1001MB23211B7BCC262B741960187392420@BN6PR1001MB2321.namprd10.prod.outlook.com>
Hello, Chris,
First, there are several places in the rte_eth_rx_queue_setup() method where -22 (-EINVAL) is returned.
See: http://dpdk.org/browse/dpdk/tree/lib/librte_ether/rte_ethdev.c#n1083
I would suggest, as a first step, that you will build dpdk with debug info for this method:
change CONFIG_RTE_LIBRTE_ETHDEV_DEBUG to be y in build/.config, and then run
make clean and make, and then please run the l3fwd app again; if there is additional info in the log, please post it here if the info still does not help you solve the problem, as it might give a hint. Also please tell which DPDK version you are using.
Regards,
Rami Rosen
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of Chris Hall
Sent: Thursday, February 09, 2017 01:14
To: users@dpdk.org
Subject: [dpdk-users] l3fwd rte_eth_rx_queue_setup: err=-22
Hello,
I’m having a bit of trouble running the l3fwd example program, I keep getting the error “rte_eth_rx_queue_setup: err=-22”
No matter what options I supply. Wondering if I’m missing something ?
Using l3fwd from dpdk-next-net
Thanks in advance.
Chris
# dpdk-devbind -s
Network devices using DPDK-compatible driver ============================================
0000:04:00.0 'SFC9220' drv=igb_uio unused=sfc
0000:04:00.1 'SFC9220' drv=igb_uio unused=sfc
# x86_64-native-linuxapp-gcc/l3fwd -l 1,2 -n 4 -w04:00.0 -w04:00.1 -- -p 0x3 --config="(0,0,1),(1,0,2)"
EAL: Detected 40 lcore(s)
EAL: Probing VFIO support...
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL: probe driver: 1924:a03 net_sfc_efx
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL: probe driver: 1924:a03 net_sfc_efx
L3FWD: LPM or EM none selected, default LPM on Initializing port 0 ...
Creating queues: nb_rxq=1 nb_txq=2...
PMD: sfc_efx 0000:04:00.0 #0: LSC tracking using interrupts is disabled
PMD: sfc_efx 0000:04:00.0 #0: FCS stripping control not supported - always stripped Address:00:0F:53:43:9D:50, Destination:02:00:00:00:00:00, Allocated mbuf pool on socket 0
LPM: Adding route 0x01010100 / 24 (0)
LPM: Adding route 0x02010100 / 24 (1)
LPM: Adding route IPV6 / 48 (0)
LPM: Adding route IPV6 / 48 (1)
txq=1,0,0 txq=2,1,0
Initializing port 1 ...
Creating queues: nb_rxq=1 nb_txq=2...
PMD: sfc_efx 0000:04:00.1 #1: LSC tracking using interrupts is disabled
PMD: sfc_efx 0000:04:00.1 #1: FCS stripping control not supported - always stripped Address:00:0F:53:43:9D:51, Destination:02:00:00:00:00:01, txq=1,0,0 txq=2,1,0
Initializing rx queues on lcore 1 ...
rxq=0,0,0 EAL: Error - exiting with code: 1
Cause: rte_eth_rx_queue_setup: err=-22, port=0
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
next prev parent reply other threads:[~2017-02-09 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 23:14 Chris Hall
2017-02-09 5:22 ` Rosen, Rami [this message]
2017-02-09 6:48 ` Andrew Rybchenko
2017-02-10 0:05 Chris Hall
2017-02-10 6:46 ` Andrew Rybchenko
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=9B0331B6EBBD0E4684FBFAEDA55776F93D4A3AFF@HASMSX110.ger.corp.intel.com \
--to=rami.rosen@intel.com \
--cc=chris.hall@stackpath.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).