All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 77] [Interrupt app]: failed to start interrupt app.
Date: Thu, 26 Jul 2018 14:41:55 +0000	[thread overview]
Message-ID: <bug-77-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=77

            Bug ID: 77
           Summary: [Interrupt app]: failed to start interrupt app.
           Product: DPDK
           Version: 18.08
          Hardware: x86
                OS: Linux
            Status: CONFIRMED
          Severity: major
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: waela@mellanox.com
  Target Milestone: ---

How to reproduce:
Start the app using the following command:

l3fwd-power -c 0xff -n 4  -w 0000:00:05.1  -w 0000:00:05.0 -- -p 0x3 -P 
--parse-ptype --config='(0, 0, 1)(1, 0, 2)(0, 1, 3)(1, 1, 4)'
Real result:

POWER: File not openned
POWER: Cannot set governor of lcore 7 to userspace
POWER: Attempting to initialise VM power management...
GUEST_CHANNEL: Opening channel
'/dev/virtio-ports/virtio.serial.port.poweragent.7' for lcore 7
GUEST_CHANNEL: Unable to to connect to
'/dev/virtio-ports/virtio.serial.port.poweragent.7' with error No such file or
directory
POWER: Unable to set Power Management Environment for lcore 7
POWER: Library initialization failed on core 7
EAL: Error - exiting with code: 1
  Cause: init_power_library failed

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2018-07-26 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 14:41 bugzilla [this message]
2018-07-26 15:21 ` [Bug 77] [Interrupt app]: failed to start interrupt app 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-77-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 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.