All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE)
Date: Mon, 11 Sep 2017 06:11:29 -0700	[thread overview]
Message-ID: <20170911131128.GD1774378@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20170910073653.GA284@x4>

Hello,

On Sun, Sep 10, 2017 at 09:36:53AM +0200, Markus Trippelsdorf wrote:
> Since:
> 
>  commit c5a94a618e7ac86b20f53d947f68d7cee6a4c6bc
>  Author: Peter Zijlstra <peterz@infradead.org>
>  Date:   Wed Aug 23 13:58:44 2017 +0200
> 
>      workqueue: Use TASK_IDLE
> 
> 
> all worker threads are in D state. They all show up when using "magic
> SysRq w". In htop they all have big fat red 'D' in the state column.
> Is this really desirable?
> 
> I have attached the output of "ps aux" after boot and the SysRq-w
> output.

Hmm.... looks like we better revert until we figure out how this
should get presented in debugging facilities / to userspace.  Peter?

Thanks.

-- 
tejun

  reply	other threads:[~2017-09-11 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-10  7:36 Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) Markus Trippelsdorf
2017-09-11 13:11 ` Tejun Heo [this message]
2017-09-11 14:21   ` Markus Trippelsdorf
2017-09-21 11:08     ` Markus Trippelsdorf
2017-09-21 12:30       ` Peter Zijlstra
2017-09-21 14:41         ` Markus Trippelsdorf
2017-09-22  9:35           ` Markus Trippelsdorf
2017-09-22 11:54             ` [RFC][PATCH] sched: Cleanup task->state printing Peter Zijlstra
2017-09-22 12:40               ` Markus Trippelsdorf
2017-09-22 14:12               ` Steven Rostedt
2017-09-22 15:56                 ` Peter Zijlstra

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=20170911131128.GD1774378@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=peterz@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.