We have CentOS 6.4 and the
kipmi0 is showing as 99.8%cpu and 0.0% memory and load average is 1.00. What should we do to rectify on this?
We have CentOS 6.4 and the
Debugging the issue
Are the other systems identical to this system? You're going to have to determine that they are. There has to be something that's fundamentally different between them. Firmware? Same RPM versions?
You can use tools such as
I'd get a good baseline of the RPMs installed by running this command on one of the systems that's not exhibiting this issue and the one that is and compare the package lists to make sure they're all at the same versions.
Then get the files on the same machine and do an sdiff of the 2 files:
Potential cause #1
The IBM website had this technote titled: Kipmi0 May Show Increased CPU Utilization on Linux, regarding this issue. According to this issue you can essentially ignore the problem.
description of issue
Potential solution #2
I found this post on someones blog simply titled: kipmi0 problem. This problem sounded identical to yours. The issue was traced to an issue with 2 kernel modules that were getting loaded as part of the
These were the 2 kernel modules:
You can manually remove these with the following commands:
To make this fix permanent, you'lll need to disable the loading of these particular kernel modules within one of the
According to the IPMI Document:
So,we can execute this command to set the kipmid_max_busy_us parameter:
In our system,after set this parameter,the cpu of kipmi0 decreased to 15%.
You can try this.
To make the changes persistent you can configure the options for the ipmi_si kernel module.
I found the following helps with this issue:
This seems to wake up IPMI and then it stops using 100% of a core.
I also found the following helpful:
Also in the past I have been able on some servers to resolve the 100% CPU usage by:
but in my most recent experience the above options would just cause
Hopefully this helps someone.
kipmi0 can be disabled on CentOS 6 entirely by adding
Test at the GRUB boot screen by highlighting the kernel you want to boot, hit 'a' to modify parameters and appending
Make permanent by appending
NOTE: In distros that have ipmi_si as a separate kernel module, using a modprobe.d conf file is more appropriate. In CentOS ipmi_si is built in to the kernel image, so modprobe configs do not work.
CentOS 6 have ipmi driver compiled in kernel. If you do not need ipmi support then just disable it grub.conf
I found this running CentOS 7 and trying to figure out what was taking it up.
For me, it was Supermicro's "ipmicfg" running from a script I wrote or something. I just pkilled it and the kipmi0 usage went away.