All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuya Mukawa <mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
To: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: rte_eal_init() causes PANIC using latest DPDK code.
Date: Mon, 19 Jan 2015 16:10:43 +0900	[thread overview]
Message-ID: <54BCADF3.1020908@igel.co.jp> (raw)

Hi,

I've got following error using latest DPDK code.
Does someone face the same issue?
In my environment, It seems almost all DPDK apps (at lease l2fwd and
testpmd) cannot work.

--------------------------------------------
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL:   cannot open VFIO container, error 2 (No such file or directory)
EAL: VFIO support could not be initialized
EAL: Setting up memory...
EAL: Ask a virtual area of 0x280000000 bytes
EAL: Virtual area found at 0x7ffd40000000 (size = 0x280000000)
EAL: Requesting 10 pages of size 1024MB from socket 0
RING: Cannot reserve memory for tailq
EAL: rte_eal_common_log_init(): cannot create log_history mempool
PANIC in rte_eal_init():
Cannot init logs
6: [./build/l2fwd() [0x41cf53]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
[0x7ffff7105ec5]]
4: [./build/l2fwd(main+0x1c) [0x41c52c]]
3: [./build/l2fwd(rte_eal_init+0x1073) [0x46a653]]
2: [./build/l2fwd(__rte_panic+0xc9) [0x41c3ff]]
1: [./build/l2fwd(rte_dump_stack+0x18) [0x471828]]
--------------------------------------------

I tried bisect, and it seems below patch causes this.
"eal: fix check for power of 2 in 0 case".


Thanks,
Tetsuya

             reply	other threads:[~2015-01-19  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19  7:10 Tetsuya Mukawa [this message]
     [not found] ` <54BCADF3.1020908-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
2015-01-19  8:53   ` rte_eal_init() causes PANIC using latest DPDK code Doherty, Declan
     [not found]     ` <345C63BAECC1AD42A2EC8C63AFFC3ADC27480FA1-kPTMFJFq+rF9qrmMLTLiibfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-01-19  8:56       ` Tetsuya Mukawa
     [not found]         ` <54BCC6C6.2050301-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
2015-01-19  9:03           ` Thomas Monjalon
2015-01-19  9:49     ` Qiu, Michael
     [not found]       ` <533710CFB86FA344BFBF2D6802E60286CB7507-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-01-19 10:06         ` Tetsuya Mukawa
2015-01-19 13:00           ` Qiu, Michael

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=54BCADF3.1020908@igel.co.jp \
    --to=mukawa-alsx/un32fvpdbfq/vqriq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.