Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1736541
| From | Markus Trippelsdorf <markus@trippelsdorf.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) |
| Date | 2017-09-21 13:10 +0200 |
| Message-ID | <us7wL-cK-25@gated-at.bofh.it> (permalink) |
| References | <uo50t-vF-9@gated-at.bofh.it> <uowN4-3M9-19@gated-at.bofh.it> <uoxSO-4tP-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2017.09.11 at 16:21 +0200, Markus Trippelsdorf wrote: > On 2017.09.11 at 06:11 -0700, Tejun Heo wrote: > > 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? > > BTW rcu recently introduced the same issue: > > commit d5374226c3e444239e063f005dfb59cae4390db4 > Author: Luis R. Rodriguez <mcgrof@kernel.org> > Date: Tue Jun 20 14:45:47 2017 -0700 > > rcu: Use idle versions of swait to make idle-hack clear Ping? You may call it a cosmetic issue, but still it makes debugging much harder. Finding "real" blocked tasks is now like finding a needle in a haystack. -- Markus
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) Tejun Heo <tj@kernel.org> - 2017-09-11 15:20 +0200
Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) Markus Trippelsdorf <markus@trippelsdorf.de> - 2017-09-11 16:30 +0200
Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) Markus Trippelsdorf <markus@trippelsdorf.de> - 2017-09-21 13:10 +0200
Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) Peter Zijlstra <peterz@infradead.org> - 2017-09-21 14:40 +0200
Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) Markus Trippelsdorf <markus@trippelsdorf.de> - 2017-09-21 16:50 +0200
Re: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use TASK_IDLE) Markus Trippelsdorf <markus@trippelsdorf.de> - 2017-09-22 11:40 +0200
[RFC][PATCH] sched: Cleanup task->state printing Peter Zijlstra <peterz@infradead.org> - 2017-09-22 14:00 +0200
Re: [RFC][PATCH] sched: Cleanup task->state printing Markus Trippelsdorf <markus@trippelsdorf.de> - 2017-09-22 14:50 +0200
Re: [RFC][PATCH] sched: Cleanup task->state printing Steven Rostedt <rostedt@goodmis.org> - 2017-09-22 16:20 +0200
Re: [RFC][PATCH] sched: Cleanup task->state printing Peter Zijlstra <peterz@infradead.org> - 2017-09-22 18:00 +0200
csiph-web