From: David Marchand <david.marchand@redhat.com>
To: oulijun <oulijun@huawei.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>
Subject: Re: [dpdk-dev] 【BUG REPORT】l3fwd-power can not exit by ctrl+c
Date: Wed, 20 May 2020 10:49:06 +0200 [thread overview]
Message-ID: <CAJFAV8xO-PBDefz_k6TW8qDygaUMgm4XLpdMTK4ZGLF7VjJPJg@mail.gmail.com> (raw)
In-Reply-To: <43c93985-27c3-354f-fc5d-749dd21b34a7@huawei.com>
On Wed, May 20, 2020 at 10:41 AM oulijun <oulijun@huawei.com> wrote:
> 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.
Please attach a gdb, list the threads running and get a backtrace on each.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2020-05-20 8:49 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 [this message]
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
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=CAJFAV8xO-PBDefz_k6TW8qDygaUMgm4XLpdMTK4ZGLF7VjJPJg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=oulijun@huawei.com \
--cc=reshma.pattan@intel.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).