I'd like to perform a bisect to identify the commit that introduced this regression. Can you test the following kernels and see which ones exhibit the bug:
4.4.19: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/ 4.4.20: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.20/ 4.4.21: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.21 You don't have to test all of them, just up until the first one shows the bug. Also, does this issue only happen with the -42 kernel? Do you know if it happens with the -39 kernel? Do you know the last kernel version that did not have the bug? Thanks in advance! ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Tags added: kernel-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633391 Title: Ubuntu doesn't boot anymore {REGRESSION} To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
