看看专业的说法： kipmi is supposed to run with low priority. When you say it consumes 70-90% of the CPUs, is that constant (does it still consume the processor when they are other tasks in the process queue that should have a larger slice of the CPU time) or the 70%/90% comes when the machine is idle? A second issue to investigate is whether you have pending controller issues (alarms of varying nature that are not resolved) and/or older versions of controller firmware.
To make the changes persistent you 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