@Eric (although you do not seem to have subscribed to this bug report).
Your issue is different than what this bug report is/was covering.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I am seeing this in Xenial running:
Linux beethoven 4.4.0-81-lowlatency #104-Ubuntu SMP PREEMPT Wed Jun 14
09:42:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I have probably 50 kworker processes, including one that is pegging a
core to 100%. Proc is AMD 8320.
Not sure this is helpful but thought
I would not expect to see this issue in 16.04, and don't on my test
16.04 server, with the default, up to date, kernel. (Linux s15
4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux).
--
You received this bug notification because you are a member of
@Colin, We were seeing it in a Xenial deployment. We have tested in our
staging environment and have not seen the issue since updating updating
to the new kernel, so it is looking good so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Peter, is this a bug in Xenial?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1649905
Title:
On boot excessive number of kworker threads are running
Status in linux package in
Is this being verified for Xenial as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1649905
Title:
On boot excessive number of kworker threads are running
Status in linux package
This bug was fixed in the package linux - 4.8.0-34.36
---
linux (4.8.0-34.36) yakkety; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1651800
* Miscellaneous Ubuntu changes
- SAUCE: Do not build the xr-usb-serial driver for s390
linux (4.8.0-33.35)
I've tested 4.8.0-34 #36 from yakkety -proposed and the issue is solved.
Marking this as verified for yakkety.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is
I tested kernel 4.10-rc1, and the issue is solved with it.
I'm not sure how to test the yakkety proposed kernel, because the
instructions seems to be for a desktop computer, and this issue shows up
much much more clearly on my server computers.
--
You received this bug notification because you
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1649905
Title:
On boot excessive number of kworker
I didn't see the third commit mentioned which I thought was also
required:
mm: memcontrol: use special workqueue for creating per-memcg caches
Anyway, I'll test also, once kernel 4.10-rc1 is ready.
The upstream bug report is this one:
https://bugzilla.kernel.org/show_bug.cgi?id=172991
** Bug
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux (Ubuntu Yakkety)
Status: New => In Progress
**
13 matches
Mail list logo
