This may be the same thing we are seeing on OpenStack compute nodes
since upgrade. Hard crash, no output to logs, local console occasionally
shows a kernel panic ending with Fatal Exception in Interrupt, shutting
down CPU's.
We are seeing this reliably across 10 nodes which have been upgraded,
Actually forget that, just worked out they are in the extras package
--
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/1383921
Title:
kipmi0 process hangs with ipmitool
Status in linux
The kernel 3.13.0-41-generic which is in proposed does not appear to
have any of the ipmi modules. Are we doing something wrong ?
root@adam:/lib/modules# uname -r
3.13.0-41-generic
root@adam:/lib/modules# modprobe ipmi_si
modprobe: FATAL: Module ipmi_si not found.
root@adam:/lib/modules#
With the kernel 3.13.0-41-generic, I can confirm that we are now able to
run warm and cold resets of the mc via ipmitool correctly. On previous
kernel those commands would cause kipmi to use 100% cpu time and require
the ipmi modules to be unloaded and reloaded before ipmitool would
operate
Is there any news on this issue ? we have many nodes in our Openstack
cluster starting to suffer from this problem as we have a puppet fact
which runs ipmitool lan print and so triggers the bug often. Could you
also tell us what the workaround was for RHEL as we can't access the
page on RedHat's
5 matches
Mail list logo
