** No longer affects: linux (Ubuntu Vivid)
--
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:
The Ubuntu 3.19.0-35.40 kernel currently has the 3.19.8-ckt8 stable
updates, so an quick test would be to install Vivid, then apply the
latest updates and check if the bug exists. However, that will not tell
us if it's already fixed in ckt10.
We know this bug is fixed in the Wily(4.2) kernel. H
Hi Joseph,
I've just checked the latest image available on GCE (which is where we'd
try to repro this), it is Ubuntu 3.19.0-33.38~14.04.1-generic
3.19.8-ckt7.
Is this worth trying? Or does it need to be ckt10?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bu
If possible, please test the latest Upstream 3.19 kernel, which can be
downloaded from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt10-vivid/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
OK thanks Joseph. We'll run a test against the latest 3.19.
--
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
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 st
It takes us a bit of time to spin up an environment large enough to hit
this, so I'm just trying to figure out how many runs we'll need to pin
this down.
What are your thoughts here? How many kernels are we likely to need to
test, and is there a way for us to get good diagnostics out to look for
That is correct. The latest Wily kernel is now newer than
4.2.0-040200rc7-generic . Do you not see this bug with the latest Wily
kernel?
--
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:
Isn't the latest Wily kernel more recent than the
4.2.0-040200rc7-generic #201508162030 we tried above (and didn't
exhibit the problem)?
--
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:
Hi Lance,
Sorry for the delay. So it sounds like this bug is a regression from
Trusty(3.13) to Vivid(3.19), but it may now be fixed in Wily since it is
based on the 4.2 kernel.
Can you confirm that the latest Wily kernel does not exhibit this bug?
If it does not, we can perform a "Reverse" bisec
We do NOT hit this when using the 4.2 kernel jsalisbury suggested
(4.2.0-040200rc7-generic #201508162030 SMP Mon Aug 17 00:31:33 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux).
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received
A little more information:
The ready-repro scenario does NOT hit this when using a 3.13 kernel
(3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64
x86_64 GNU/Linux) - though Shaun said that in the first post.
If I upgrade my 3.13 VM image to 3.19 (usingapt-get instal
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.2 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
What diags would be useful for this bug? I've got a reliable repro
scenario, but its not a simple one (setup 110 GCE nodes and send 700
routes into BIRD).
I've tried configuring crashdump on my GCE nodes, but I can't seem to
get crashkernel=384M-2G:64M,2G-:128M into the kernel command line on
GCE
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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:
Kern
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
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 bu
16 matches
Mail list logo
