[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151029022447.GB27115@mtj.duckdns.org>
Date: Thu, 29 Oct 2015 11:24:47 +0900
From: Tejun Heo <htejun@...il.com>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: cl@...ux.com, akpm@...ux-foundation.org, mhocko@...nel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, hannes@...xchg.org, mgorman@...e.de
Subject: Re: [patch 3/3] vmstat: Create our own workqueue
Hello,
That's weird.
On Wed, Oct 28, 2015 at 08:57:28PM +0900, Tetsuo Handa wrote:
> [ 272.851035] Showing busy workqueues and worker pools:
> [ 272.852583] workqueue events: flags=0x0
> [ 272.853942] pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=1/256
> [ 272.855781] pending: vmw_fb_dirty_flush [vmwgfx]
> [ 272.857500] pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
> [ 272.859359] pending: vmpressure_work_fn
> [ 272.860840] workqueue events_freezable_power_: flags=0x84
> [ 272.862461] pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256
> [ 272.864479] in-flight: 11286:disk_events_workfn
What's this guy doing? Can you get stack dump on 11286 (or whatever
is in flight in the next lockup)?
> [ 272.866065] pending: disk_events_workfn
> [ 272.867587] workqueue vmstat: flags=0x8
> [ 272.868942] pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
> [ 272.870785] pending: vmstat_update
> [ 272.872248] pool 2: cpus=1 node=0 flags=0x0 nice=0 workers=4 idle: 14 218 43
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists