From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: thousands of kworker processes with 4.7.x and 4.8-rc*
Date: Sat, 24 Sep 2016 01:15:40 +0900 [thread overview]
Message-ID: <50d06a3b797091821d190196b48e8d52@admin.virtall.com> (raw)
In-Reply-To: <1474639800.4025.29.camel@gmail.com>
On 2016-09-23 23:10, Mike Galbraith wrote:
>> I did some experiments to see when the problem first appeared.
>> Thousands
>> of kworker processes start to show up in 4.7.0-rc5.
>>
>> kernel version | kworker count after boot
>> -------------------------------------------
>> 4.6.3 > > 37
>> 4.6.4 > > 47
>> 4.6.5 > > 46
>> 4.6.6 > > 49
>> 4.6.7 > > 49
>> 4.7.0-rc1 > > 46
>> 4.7.0-rc2 > > 49
>> 4.7.0-rc3> > 45
>> 4.7.0-rc4> > 47
>> 4.7.0-rc5> > 1592
>
> Best bet would be to use 'git bisect' to locate the exact commit that
> caused this, and post the bisection result along with your config.
>
> AFAIK, nobody else is seeing this, is the kernel virgin source?
Yes, it's a kernel.org kernel.
I found some similar reports, though without much more info:
https://github.com/zfsonlinux/zfs/issues/5036 - kernel 4.7.2, initially
attributed to ZFS on Linux, but then reproduced without ZFS
https://github.com/systemd/systemd/issues/4069 - kernel 4.7.2
I'll try to bisect.
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2016-09-23 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 7:08 thousands of kworker processes with 4.7.x and 4.8-rc* Tomasz Chmielewski
2016-09-23 13:23 ` Tomasz Chmielewski
2016-09-23 14:10 ` Mike Galbraith
2016-09-23 16:15 ` Tomasz Chmielewski [this message]
[not found] ` <a08b61cee6c43de99ac3c6a8cacfdc04@admin.virtall.com>
2016-09-25 12:40 ` Tomasz Chmielewski
2016-09-25 17:21 ` Mike Galbraith
2016-09-25 18:22 ` Mike Galbraith
2016-09-25 19:07 ` Nikolay Borisov
2016-09-27 3:49 ` Tomasz Chmielewski
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=50d06a3b797091821d190196b48e8d52@admin.virtall.com \
--to=mangoo@wpkg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=umgwanakikbuti@gmail.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).