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 13903A0093; Wed, 20 May 2020 13:37:24 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 58A511C2AA; Wed, 20 May 2020 13:37:23 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id E61C11C2A5 for ; Wed, 20 May 2020 13:37:21 +0200 (CEST) IronPort-SDR: eN1YIpTAdQq47KEINEZk1LTESMwBBWCmmoxZ13XeZtJE03FUNh/DeS2x3vqqmzmbyTqNtoJaO3 5TLjpAfgAQtg== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 May 2020 04:37:20 -0700 IronPort-SDR: VqOuho0v60Ko6D8+YjQYZL44rySaIDnU7+H7VcPNnkXWrP3uLaHVCjTpn8G/rNB/ESZ/tTUvxM oFVMy9gfy7Tg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,413,1583222400"; d="scan'208";a="299905120" 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 04:37:19 -0700 To: oulijun , David Marchand Cc: Van Haaren Harry , dev , David Hunt , "Pattan, Reshma" References: <43c93985-27c3-354f-fc5d-749dd21b34a7@huawei.com> From: "Burakov, Anatoly" Message-ID: <27c29ab0-5c88-0baa-6496-aa39b3f1cb82@intel.com> Date: Wed, 20 May 2020 12:37:18 +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: <43c93985-27c3-354f-fc5d-749dd21b34a7@huawei.com> 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 9:41 AM, oulijun wrote: > > > 在 2020/5/20 15:22, David Marchand 写道: >> Hello, >> >> On Wed, May 20, 2020 at 5:18 AM oulijun wrote: >>>      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. >> >> We had a fix in rc1 that is supposed to fix this. >> https://git.dpdk.org/dpdk/commit?id=613ce6691c0d5ac0f99d7995f1e8e4ac86643882 >> >> >> Copying Anatoly and David H. too. Yes, and also this fix: https://git.dpdk.org/dpdk/commit/?id=f4d1e19c293dc95073614f630ea729cf0bfb57b7 It's part of rc2 as well. With the above two fixes, all problems with quitting the app should have been fixed (and were fixed, according to our testing). >> >> >>> >>> 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 >>> [root@centos-C3 build]# >> >> So I understand those traces are for when it works. >> >> What about the traces when it does not work? Yes, supplying log "when it worked" is not helpful if the goal is to figure out what went wrong :) >> Can you get a backtrace to know where the process is stuck? > I think that it is entered the rte_exit and can not eixt >> >> >> Thanks for reporting. >> > the log as follows when it not works: > 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 Again, this looks like a pre-rc1 log. Please retest with latest rc2 code. > > > > > it can not exit and enter the shell window. > > Thanks > -- Thanks, Anatoly