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.
Before we start the bisect, can you first confirm that 3.19 final does not have the bug an 4.0-rc1 does have it? The two kernels can be downloaded from: v3.19 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ 4.0-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/ Thanks in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Wily) Importance: Medium Status: Confirmed ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Wily) Status: Confirmed => In Progress ** Bug watch added: Linux Kernel Bug Tracker #53071 http://bugzilla.kernel.org/show_bug.cgi?id=53071 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=53071 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491467 Title: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1491467/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
