From: "Hunt, David" <david.hunt@intel.com>
To: oulijun <oulijun@huawei.com>, David Marchand <david.marchand@redhat.com>
Cc: Van Haaren Harry <harry.van.haaren@intel.com>, dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] 【BUG REPORT】l3fwd-power can not exit by ctrl+c
Date: Wed, 27 May 2020 09:21:37 +0100 [thread overview]
Message-ID: <9e0f9c46-149f-e0f9-9c6f-f0945b864ecb@intel.com> (raw)
In-Reply-To: <3e767dfd-609e-9edc-a18d-f6129bd9072d@huawei.com>
On 27/5/2020 7:10 AM, oulijun wrote:
>
>
> 在 2020/5/26 16:36, Hunt, David 写道:
>> Hi Lijun,
>>
>> On 26/5/2020 4:50 AM, oulijun wrote:
>>> Hi，
>>> I have update the code into 20.05-rc2. However， the l3fwd-power
>>> startup fail.
>>>
>>> [root@centos-C3 build]# l3fwd-power -w 0000:7d:00.1 -c 0xc000000 -n
>>> 4 -- -P -p 0x01 --config '(0,0,27)' --parse-ptype
>>>
>>
>> --snip--
>>
>>> POWER: Attempting to initialise ACPI cpufreq power management...
>>> POWER: Power management governor of lcore 26 has been set to user
>>> space successfully
>>> POWER: File not opened
>>> POWER: Cannot get available frequencies of lcore 26
>>> POWER: Attempting to initialise PSTAT power management...
>>> POWER: Power management governor of lcore 26 has been set to
>>> performance successfully
>>> POWER: Error opening '/dev/cpu/26/msr': No such file or directory
>>> POWER: Cannot init for setting frequency for lcore 26
>>
>>
>> This was not happening in your previous logs, have you got the 'msr'
>> kernel module loaded?
>>
>>> POWER: Attempting to initialise VM power management...
>>> GUEST_CHANNEL: Opening channel
>>> '/dev/virtio-ports/virtio.serial.port.poweragent.26' for lcore 26
>>> GUEST_CHANNEL: Unable to to connect to
>>> '/dev/virtio-ports/virtio.serial.port.poweragent.26' with error No
>>> such file or directory
>>
>>
>> I did not see any GUEST_CHANNEL notifications in the previous logs
>> you provided, has your setup changed in any way?
>>
>> By the way, I can run the command you provided above (without the
>> whitelist) without any errors on my system, and a single CTRL-C exits
>> gracefully. I am not running in a VM.
>>
>> Rgds,
>> Dave.
>>
> Is your hardware system x86? My system is arm64
>>
>> .
>>
>
I'm on an x86 system.
Rgds,
Dave.
next prev parent reply other threads:[~2020-05-27 8:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 3:18 oulijun
2020-05-20 7:22 ` David Marchand
2020-05-20 8:41 ` oulijun
2020-05-20 8:49 ` David Marchand
2020-05-20 11:37 ` Burakov, Anatoly
2020-05-22 8:17 ` oulijun
2020-05-22 9:00 ` Burakov, Anatoly
2020-05-22 9:02 ` Hunt, David
2020-05-26 3:50 ` oulijun
2020-05-26 8:36 ` Hunt, David
2020-05-26 9:11 ` oulijun
2020-05-27 6:10 ` oulijun
2020-05-27 8:21 ` Hunt, David [this message]
2020-05-26 9:24 ` Burakov, Anatoly
2020-05-27 6:04 ` oulijun
2020-05-27 8:57 ` Burakov, Anatoly
2020-05-20 9:45 ` Burakov, Anatoly
2020-05-21 1:26 ` oulijun
2020-05-21 10:46 ` Burakov, Anatoly
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=9e0f9c46-149f-e0f9-9c6f-f0945b864ecb@intel.com \
--to=david.hunt@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=oulijun@huawei.com \
--cc=reshma.pattan@intel.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).