Google can not find much information, see a saying: is some platform Interface manager. Do not dare to kill, and then check the data.
Look at the professional saying:
KIPMI is supposed to run with the low priority. When you say it consumes 70-90% of the CPUs, was that constant (does it still consume the processor when they are other TAS KS in the process queue this should have a larger slice of the CPU time) or the 70%/90% comes when the machine is idle?
A second issue to investigate are whether you have pending controller issues (alarms of varying-nature-are not resolve d) and/or older versions of Controller firmware.
View service Chkconfig found that only approximate IPMIEVD services, it is estimated that this, with the information on the internet said the IPMI discrepancy!
FIX: No repair required
The code is as follows |
|
No fix required. You are should ignore increased CPU utilization as it has no impact on actual system performance. |
Although this is a use of spare CPU resources to do some interface automatic adjustment task, but look at the amount of resources still afraid of accidents.
Find: Can temporarily reduce
The code is as follows |
|
echo >/sys/module/ipmi_si/parameters/kipmid_max_busy_us www.111cn.net In our System,after set this parameter,the CPU of the kipmi0 decreased to 15%. |
When you do execute the above command, the CPU's single core resources are reduced from 100% to 10%.
Can try this. Permanent reduction
The code is as follows |
|
To make the changes persistent your can configure the options for the Ipmi_si kernel module. Create a file in/etc/modprobe.d/, i.e./etc/modprobe.d/ipmi.conf, and add the following content: # prevent Kipmi0 from consuming 100% CPU Options Ipmi_si kipmid_max_busy_us=100 |
It's written in, but it's not reboot test yet.