From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: oulijun <oulijun@huawei.com>,
david.marchand@redhat.com, harry.van.haaren@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 【BUG REPORT】l3fwd-power can not exit by ctrl+c
Date: Thu, 21 May 2020 11:46:24 +0100 [thread overview]
Message-ID: <4db44399-7a1d-b28c-0ce9-2705b6c0e6cd@intel.com> (raw)
In-Reply-To: <c8738c56-e322-c503-6282-37c7dd54612e@huawei.com>
On 21-May-20 2:26 AM, oulijun wrote:
>
>
> 在 2020/5/20 17:45, Burakov, Anatoly 写道:
>> On 20-May-20 4:18 AM, oulijun wrote:
>>> Hi, David Marchand && guys
>>>
>>> I am using 20.05-rc2 version to test based on HNS3 NIC hardware,
>>> and found that after starting l3fwd-power,
>>>
>>> using ctrl+c cannot force quit. But I revert the patch(33666b4
>>> service: fix crash on exit) and it is ok.
>>>
>>> the log as follows:
>>>
>>> Initializing rx queues on lcore 26 ...
>>> Initializing rx queues on lcore 27 ... rxq=0,0,0 Port 0: softly parse
>>> packet type info
>>>
>>>
>>> Checking link status...............0000:7d:00.1
>>> hns3_update_link_status(): Link status change to up!
>>> done
>>> Port 0 Link Up - speed 25000 Mbps - full-duplex
>>> L3FWD_POWER: entering main loop on lcore 27
>>> L3FWD_POWER: -- lcoreid=27 portid=0 rxqueueid=0
>>> L3FWD_POWER: lcore 26 has nothing to do
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0
>>> L3FWD_POWER: lcore 27 sleeps until interrupt triggers
>>> ^CPOWER: Power management governor of lcore 26 has been set back to
>>> successfully
>>> POWER: Power management of lcore 26 has exited from 'userspace' mode
>>> and been set back to the original
>>> POWER: Power management governor of lcore 27 has been set back to
>>> successfully
>>> POWER: Power management of lcore 27 has exited from 'userspace' mode
>>> and been set back to the original
>>> 0000:7d:00.1 hns3_dev_close(): Close port 0 finished
>>> User forced exit
>>
>> The "user forced exit" string is from before the patches were applied.
>> You are obviously not using the rc2 version. Please pull down the
>> latest l3fwd-power code and retest.
>>
> sorry, our version is 20.05-rc0
Yep. The bug you are reporting has been partially fixed in rc1, and
fully fixed in rc2. So, please test rc2.
>>> [root@centos-C3 build]#
>>>
>>> Thanks
>>>
>>> Lijun Ou
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
--
Thanks,
Anatoly
prev parent reply other threads:[~2020-05-21 10:46 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
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 [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=4db44399-7a1d-b28c-0ce9-2705b6c0e6cd@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=oulijun@huawei.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).