I'd like to perform a kernel bisect to figure out which commit caused this regression. We need to identify the earliest kernel that did not exhibit the bug and the first kernel that did exhibit the bug.
Can you test the following kernels and post back? v4.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/ If v4.4 final exhibits the bug, we should move on to testing some of the v4.4 release candidates. v4.4-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/ If v4.4-rc4 does not exhibit the bug then test v4.4-rc6: v4.4-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc6-wily/ If v4.4-rc4 does exhibit the bug then test v4.4-rc2: v4.4-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc2-wily/ If all of the 4.4 kernels going back to 4.4-rc1 have the bug, then we will have to test some 4.3 kernels. Thanks in advance! ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** 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/1544798 Title: high load with 4.4 and 4.5 kernels for Intel Mobile processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
