Next time this happens, please check the ilo for a massive backlog of
nbd kernel messages. I suspect it's nbd's insane logging rate (tens of
thousands of lines per second) endlessly growing the serial console
backlog. "dmesg -D" appears to be a quick way to fix machines in this
state, or prevent
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1500739
Title:
CPU lockup on HP Proliant DL380 Gen9 servers
Status in linux
I uploaded a crashdump of a very similar issue in LP#1505564, FYI.
--
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/1500739
Title:
CPU lockup on HP Proliant DL380 Gen9 servers
Status in
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
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/1500739
Title:
CPU lockup on HP Proliant DL380 Gen9 servers
Status in linux
Initially this looked similar to bug 1413540.
This bug patched 3.13 with 9242b5b to _mitigate_ the issue, but this patch is
already present in 3.16. So perhaps we're hitting another failure mode.
It would be good to know if the smp_call_function_* path in the backtrace is
actually leading up to
FYI I just opened #1505564, which is very similar and probably a
duplicate.
--
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/1500739
Title:
CPU lockup on HP Proliant DL380 Gen9 servers
2nd of the lockups.
** Attachment added: "CPU Lockup 2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478313/+files/cpu-lockup-2.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The first of the lockups. These all required us to hard reset the
servers via the ilo.
** Attachment added: "CPU Lockup 1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478312/+files/cpu-lockup-1.log
--
You received this bug notification because you are a
3rd of the lockups
** Attachment added: "CPU Lockup 3"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478314/+files/cpu-lockup-3.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected trusty uec-images
** Description changed:
Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
servers lock up with a similar looking cpu lockup bug. All 3 of these
servers are nova-compute nodes in an OpenStack cluster,
Unfortunately we're unable to test the latest upstream kernel in this
situation. These servers are running a production system, and as they
use bcache we need a kernel that supports it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 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
12 matches
Mail list logo
