Re: [dpdk-dev] 【BUG REPORT】l3fwd-power can not exit by ctrl+c

["Burakov, Anatoly" <anatoly.burakov@intel.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