@jsalisbury I looked at reporting upstream, and have the email ready, but I think they expect the bisect to be done also.
I checked the mainline builds and it seems to be when my machine was updated from 3.10 to 3.11. That is, I can confirm that running v3.10.9-saucy installed [1] I cannot reproduce the bug (suspend works perfectly multiple times without crazy kworker threads), while v3.11-rc1 [2] breaks exactly as per the description. I'm not sure (a) if that makes sense, and (b) how I can bisect between those. I assume I'll need to go further back in the 3.11 branch upstream to where it was branched? Let me know if there are specific instructions. Thanks! [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10.9-saucy/ [2] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/ -- 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 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
