I have this bug coming back and bite me again.
Obviously, kworker hogging CPU can be caused by multiple causes. Since
this bug report is generic in nature, maybe it should be converted as a
wish for a mean to trace easily the kworker thread. We need something
like 'top', to tell us why kworker is working so hard.
Any expert out there on kworker? Your opinion on this issue would be
much appreciated. This issue is a serious blow for the user's
experience.
** Changed in: linux (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/887793/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
