I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug: v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring v3.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy v3.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** 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/1223851 Title: High CPU load after resuming on Samsung NP550P5C in BIOS mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
