DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Gholam Reza Rahimi <rahimi.r.g@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] QoS scheduler example fails to run
Date: Mon, 21 Sep 2015 10:09:02 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126478D5BE2@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CADMHGuDX43_xgv_u++s-cx_6xztB1bb0AJtp5VbTF1XCQdmZbA@mail.gmail.com>

Hi Reza,

As your log displays below, you have an error in EAL initialization:

EAL: Error - exiting with code: 1

I suggest you try to dig up the source code to understand which is the line of code triggering this error in your system and why.

Regards,
Cristian 

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gholam Reza
> Rahimi
> Sent: Thursday, September 17, 2015 11:53 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] QoS scheduler example fails to run
> 
> Hi all,
> 
> I'm trying to run QoS scheduler example based on the information which has
> been posted in
> "http://dpdk.org/doc/guides/sample_app_ug/qos_scheduler.html"
> with DPDK 2.1.0.
> 
> I have been trying different hugepage sizes (2MByte, 1GByte), but I have
> received the same error for both.
> 
> I have pasted the output to the end of this email.
> 
> Any kind of help will be appreciated.
> 
> Regards,
> Reza
> 
> 
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Detected lcore 4 as core 4 on socket 0
> EAL: Detected lcore 5 as core 5 on socket 0
> EAL: Detected lcore 6 as core 6 on socket 0
> EAL: Detected lcore 7 as core 7 on socket 0
> EAL: Detected lcore 8 as core 0 on socket 1
> EAL: Detected lcore 9 as core 1 on socket 1
> EAL: Detected lcore 10 as core 2 on socket 1
> EAL: Detected lcore 11 as core 3 on socket 1
> EAL: Detected lcore 12 as core 4 on socket 1
> EAL: Detected lcore 13 as core 5 on socket 1
> EAL: Detected lcore 14 as core 6 on socket 1
> EAL: Detected lcore 15 as core 7 on socket 1
> EAL: Detected lcore 16 as core 0 on socket 0
> EAL: Detected lcore 17 as core 1 on socket 0
> EAL: Detected lcore 18 as core 2 on socket 0
> EAL: Detected lcore 19 as core 3 on socket 0
> EAL: Detected lcore 20 as core 4 on socket 0
> EAL: Detected lcore 21 as core 5 on socket 0
> EAL: Detected lcore 22 as core 6 on socket 0
> EAL: Detected lcore 23 as core 7 on socket 0
> EAL: Detected lcore 24 as core 0 on socket 1
> EAL: Detected lcore 25 as core 1 on socket 1
> EAL: Detected lcore 26 as core 2 on socket 1
> EAL: Detected lcore 27 as core 3 on socket 1
> EAL: Detected lcore 28 as core 4 on socket 1
> EAL: Detected lcore 29 as core 5 on socket 1
> EAL: Detected lcore 30 as core 6 on socket 1
> EAL: Detected lcore 31 as core 7 on socket 1
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 32 lcore(s)
> EAL: Setting up physically contiguous memory...
> EAL: Ask a virtual area of 0x200000000 bytes
> EAL: Virtual area found at 0x7f9740000000 (size = 0x200000000)
> EAL: Ask a virtual area of 0x200000000 bytes
> EAL: Virtual area found at 0x7f9500000000 (size = 0x200000000)
> EAL: Requesting 8 pages of size 1024MB from socket 0
> EAL: Requesting 8 pages of size 1024MB from socket 1
> EAL: TSC frequency is ~2094950 KHz
> EAL: Master lcore 1 is ready (tid=5b208900;cpuset=[1])
> EAL: lcore 7 is ready (tid=5930d700;cpuset=[7])
> EAL: lcore 5 is ready (tid=59b0e700;cpuset=[5])
> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:02:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   PCI memory mapped at 0x7f9940000000
> EAL:   PCI memory mapped at 0x7f9940100000
> PMD: eth_igb_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x1521
> EAL: PCI device 0000:02:00.2 on NUMA socket 0
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:02:00.3 on NUMA socket 0
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   PCI memory mapped at 0x7f9940104000
> EAL:   PCI memory mapped at 0x7f9940204000
> PMD: eth_igb_dev_init(): port_id 1 vendorID=0x8086 deviceID=0x1521
> APP: Initializing port 0... PMD: eth_igb_rx_queue_setup():
> sw_ring=0x7f9815b96040 hw_ring=0x7f9815b96480 dma_addr=0x4d5b96480
> PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance,
> consider
> setting the TX WTHRESH value to 4, 8, or 16.
> PMD: eth_igb_tx_queue_setup(): sw_ring=0x7f9815b84ec0
> hw_ring=0x7f9815b85f00 dma_addr=0x4d5b85f00
> PMD: eth_igb_start(): <<
> done:  Link Up - speed 1000 Mbps - full-duplex
> APP: Initializing port 1... PMD: eth_igb_rx_queue_setup():
> sw_ring=0x7f9815b74840 hw_ring=0x7f9815b74c80 dma_addr=0x4d5b74c80
> PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance,
> consider
> setting the TX WTHRESH value to 4, 8, or 16.
> PMD: eth_igb_tx_queue_setup(): sw_ring=0x7f9815b636c0
> hw_ring=0x7f9815b64700 dma_addr=0x4d5b64700
> PMD: eth_igb_start(): <<
> done:  Link Up - speed 1000 Mbps - full-duplex
> SCHED: Low level config for pipe profile 0:
>     Token bucket: period = 3277, credits per period = 8, size = 1000000
>     Traffic classes: period = 5000000, credits per period = [12207, 12207,
> 12207, 12207]
>     Traffic class 3 oversubscription: weight = 0
>     WRR cost: [1, 1, 1, 1], [1, 1, 1, 1], [1, 1, 1, 1], [1, 1, 1, 1]
> EAL: Error - exiting with code: 1

      reply	other threads:[~2015-09-21 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 20:53 Gholam Reza Rahimi
2015-09-21 10:09 ` Dumitrescu, Cristian [this message]

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=3EB4FA525960D640B5BDFFD6A3D89126478D5BE2@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=rahimi.r.g@gmail.com \
    /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).