Testing the latest upstream kernel will tell us if this bug is already fixed in mainline. If it is fixed, we can then work to identify the commit that fixes the bug.
An alternative would be to perform a kernel bisect, which will identify the commit that introduced the regression. However, that will require testing about 7 - 10 test kernels. Is it not possible to test any test kernels on the affected system? ** Tags added: needs-bisect regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592597 Title: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630 Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Bug description: Following recent update to 3.13.0-88, R630 on Trusty panics on boot. Recovery boot just hangs. 3.13.0-87 was able to be booted normally once, then kernel panics on subsequent attempts. Booting is successful with the previously running kernel, 3.13.0-61. will upload an sosreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
