Thanks for testing, Michael. Yes, I'm using the upstream kernel version tags for the bisect. So what I did was: 1. clone the mainline tree. 2. Start the bisect and enter the last good and first bad kernel versions: git bisect start git bisect good v3.10 git bisect bad v3.11-rc1
git then returned the first SHA1 to test, which was 1286da8bc009cb2aee7f285e94623fc974c0c983 I built a test kernel up to that commit, which you tested and found did not have the bug. I then used your test result to tell git the kernel with commit 1286da8 as the tip did not have the bug: git bisect good 1286da8bc009cb2aee7f285e94623fc974c0c983 git then calculated the next SHA1 which is: 1b375dc30710180c4b88cc59caba6e3481ec5c8b I'll build a test kernel up to that commit now and post the kernel shortly. We can then repeat the process. A bisect like this usually takes about 7 to 10 cycles to figure out the offending commit. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
