DPDK usage discussions
 help / color / mirror / Atom feed
From: "Matthias Pölzinger" <matt@reallyloves.beer>
To: <users@dpdk.org>
Subject: [dpdk-users] rte_eth_rx_queue_setup:err=-22
Date: Fri, 13 Sep 2019 19:19:01 +1000	[thread overview]
Message-ID: <A29F58B7-DBF5-46D1-A6E3-A6C1B7F03428@reallyloves.beer> (raw)

Hi,

 

I‘m currently trying to get a dpdk based application running, but I’m a bit unsure about the following error:

 

EAL: Error - exiting with code: 1

  Cause: rte_eth_rx_queue_setup:err=-22, port=0

 

 

I already compiled dpdk with debug option on and the changed default as suggested in this thread:

 

http://mails.dpdk.org/archives/users/2017-February/001524.html

 

But I’m not getting further. This is the current debug output:

 

EAL: Detected 4 lcore(s)

EAL: No free hugepages reported in hugepages-1048576kB

EAL: Probing VFIO support...

EAL: PCI device 0000:03:00.0 on NUMA socket -1

EAL:   Invalid NUMA socket, default to 0

EAL:   probe driver: 15ad:7b0 net_vmxnet3

EAL: PCI device 0000:0b:00.0 on NUMA socket -1

EAL:   Invalid NUMA socket, default to 0

EAL:   probe driver: 15ad:7b0 net_vmxnet3

EAL: PCI device 0000:13:00.0 on NUMA socket -1

EAL:   Device is blacklisted, not initializing

rte_mempool_ops_get_capabilities: Function not supported

rte_mempool_ops_register_memory_area: Function not supported

rte_mempool_ops_get_capabilities: Function not supported

TX Skipping disabled port 0

TX Skipping disabled port 1

Setting up hash table for lcore 1, on socket 0

Setting up hash table for lcore 2, on socket 0

Setting up hash table for lcore 3, on socket 0

setting up rx queue on port 0, queue 0

rte_eth_rx_queue_setup: Invalid RX queue_id=0

EAL: Error - exiting with code: 1

  Cause: rte_eth_rx_queue_setup:err=-22, port=0

 

I’m currently not sure if the problem is related to my dpdk setup or the code where this error is happening:

 

    /* Init RX queues */

    for (lcore_id = 0; lcore_id < RTE_MAX_LCORE; lcore_id++) {

        if (rte_lcore_is_enabled(lcore_id) == 0)

            continue;

        qconf = &lcore_conf[lcore_id];  

        for(queue = 0; queue < qconf->n_rx_queue; ++queue) {

            portid = qconf->rx_queue_list[queue].port_id;

            queueid = qconf->rx_queue_list[queue].queue_id;

 

            printf("setting up rx queue on port %u, queue %u\n", portid, queueid);  

            ret = rte_eth_rx_queue_setup(portid, queueid, nb_rxd,

                             rte_eth_dev_socket_id(portid),

                         NULL,

                         dpdklatency_pktmbuf_pool);

            if (ret < 0)

                rte_exit(EXIT_FAILURE, "rte_eth_rx_queue_setup:err=%d, port=%u\n",

                      ret, (unsigned) portid);

        }

    }

 

Happy about any clue!

 

Thanks for your support,

Matt


                 reply	other threads:[~2019-09-13  9:19 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=A29F58B7-DBF5-46D1-A6E3-A6C1B7F03428@reallyloves.beer \
    --to=matt@reallyloves.beer \
    --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).