DPDK patches and discussions
 help / color / mirror / Atom feed
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 09:22:15 +0200
Message-ID: <CAJFAV8ypMk83bFr==5B8+y6q-2fhurjK2ZPx10vvr_i6BV=_gA@mail.gmail.com> (raw)
In-Reply-To: <aca740da-e15d-7708-5bf6-a5726c13bcdd@huawei.com>

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?


Thanks for reporting.

-- 
David Marchand


  reply	other threads:[~2020-05-20  7:22 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 [this message]
2020-05-20  8:41   ` oulijun
2020-05-20  8:49     ` David Marchand
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='CAJFAV8ypMk83bFr==5B8+y6q-2fhurjK2ZPx10vvr_i6BV=_gA@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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git