From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 236] primary-secondary model is failing
Date: Mon, 01 Apr 2019 09:19:39 +0000 [thread overview]
Message-ID: <bug-236-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190401091939.VytcuFefrghI9ZJI9S63MfNWFFfmyIVLTEU5DLtwnr8@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=236
Bug ID: 236
Summary: primary-secondary model is failing
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: major
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
OS: 4.15.0-46-generic
GCC: gcc version 7.3.0
DPDK version: (git log) commit a2fe4c1b3803f3b4c060c03fd51fdc376c05ec43 (HEAD
-> master, origin/master, origin/HEAD)
Error Log:
EAL: FATAL: Cannot init tail queues for objects
EAL: Cannot init tail queues for objects
EAL: Error - exiting with code: 1
Cause: Invalid EAL arguments
Options Used: with and without '--legacy-mem'
Steps:
1. Get the specified version.
2. Build for target.
3. Build example application (helloworld and l2fwd)
4. Helloworld primary-secondary works.
5. l2fwd primary and procinfo|pdump secondary fails.
thanks
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-01 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 9:19 bugzilla [this message]
2019-04-01 9:19 ` bugzilla
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=bug-236-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).