It would take testing of 7-10 test kernels to perform a reverse bisect.
A reverse bisect will identify the exact commit that fixes this in Wily,
so we can then SRU it to Vivid.
It could also be that the fix in the 4.2 kernel was cc'd to stable and
Vivid will eventually get it through the normal stable update process.
One test we would probably want to do before performing the reverse
bisect is to test the latest 3.19 upstream stable kernel to see if it
already has the fix.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu Wily)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484919
Title:
Kernel oops associated with BIRD/netlink
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484919/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
