The kworker processes are generic in that they can do work for many kernel
parts,
so a particular kworker/number unfortunately doesn't help much to understand the
actual thing that the kworker was doing; we'll need the stack traces for that.
:)
Yes, if and once the issue starts happening again, please collect the stack
traces with the previous commands, and upload the tarball to this bug.
I'll mark the bug as Incomplete, and it should automatically expire in 60 days
iirc if there's no further activity (i.e., problem really vanished/no uploads.)
Thanks,
Mauricio
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896519
Title:
kworker consumes 80% of CPU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896519/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
