We can perform a kernel bisect to identify the commit that introduced this regression. Do you happen to know the last kernel version that did not exhibit this bug? If not, can you test the following kernels:
v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/ v3.11-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/ v3.11-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/ v3.11-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! ** Tags added: performing-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread consuming 99.8 - 100% CPU after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
