From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 57928A0093; Wed, 20 May 2020 11:45:26 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2B3621C43C; Wed, 20 May 2020 11:45:26 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id A31831C193 for ; Wed, 20 May 2020 11:45:24 +0200 (CEST) IronPort-SDR: peWO4WsUSw6PAVGj7AlLNMvC1N8t0Ii35GtzgYhykIEH0E8lT3CP5Ez3G19E18o7DoQjLAy4ng bWDdU2Y6d4zw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 May 2020 02:45:23 -0700 IronPort-SDR: UtdomiYY9T/M+XaZXmVNJz8614dptfSLyO+ZLGLeN3urPGIm+osgXtRQFI5R3h+rlIxowUK6Xp TAsiLeDUGSwQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,413,1583222400"; d="scan'208";a="299880865" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.213.167.235]) ([10.213.167.235]) by fmsmga002.fm.intel.com with ESMTP; 20 May 2020 02:45:22 -0700 To: oulijun , david.marchand@redhat.com, harry.van.haaren@intel.com Cc: dev@dpdk.org References: From: "Burakov, Anatoly" Message-ID: Date: Wed, 20 May 2020 10:45:21 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] =?utf-8?b?44CQQlVHIFJFUE9SVOOAkWwzZndkLXBvd2VyIGNhbiBu?= =?utf-8?q?ot_exit_by_ctrl+c?= X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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. > [root@centos-C3 build]# > > Thanks > > Lijun Ou > > > > > > -- Thanks, Anatoly