From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E49DFA0093; Wed, 20 May 2020 10:42:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 748FE1C1B3; Wed, 20 May 2020 10:42:02 +0200 (CEST) Received: from huawei.com (szxga07-in.huawei.com [45.249.212.35]) by dpdk.org (Postfix) with ESMTP id 85D2C1BFD7 for <dev@dpdk.org>; Wed, 20 May 2020 10:41:51 +0200 (CEST) Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 00EC35EEF3DA4A5627F1; Wed, 20 May 2020 16:41:34 +0800 (CST) Received: from [127.0.0.1] (10.67.103.119) by DGGEMS408-HUB.china.huawei.com (10.3.19.208) with Microsoft SMTP Server id 14.3.487.0; Wed, 20 May 2020 16:41:33 +0800 To: 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>, David Hunt <david.hunt@intel.com>, "Pattan, Reshma" <reshma.pattan@intel.com> References: <aca740da-e15d-7708-5bf6-a5726c13bcdd@huawei.com> <CAJFAV8ypMk83bFr==5B8+y6q-2fhurjK2ZPx10vvr_i6BV=_gA@mail.gmail.com> From: oulijun <oulijun@huawei.com> Message-ID: <43c93985-27c3-354f-fc5d-749dd21b34a7@huawei.com> Date: Wed, 20 May 2020 16:41:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <CAJFAV8ypMk83bFr==5B8+y6q-2fhurjK2ZPx10vvr_i6BV=_gA@mail.gmail.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.103.119] X-CFilter-Loop: Reflected 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> 在 2020/5/20 15:22, David Marchand 写道: > Hello, > > On Wed, May 20, 2020 at 5:18 AM oulijun <oulijun@huawei.com> 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. > > >> >> 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? > 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 it can not exit and enter the shell window. Thanks