Stopping the kipmi0 kernel thread?

[George Magklaras]

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.

GM

Kenneth Holter wrote:
> Hello.
> 
> 
> A couple of our Dell 1950 running RHEL 5.4 have since a RHEL 5.2 -> 5.4
> upgrade (and a reboot) started to have the kipmi0 kernel thread running
> (again), consuming 70-90% CPU. As far as I understand, this process is
> probably related to Dell Openmanage. Is it so that the Dell Openmanage
> processes issues IPMI commands, and the kipmi0 kernel thread is used for
> speeding up these commands? If so, I probably shouldn't kill this thread.
> But is there a way to make is use less CPU time, since this shows up in our
> monitoring software as critical alarms?
> 
> 
> Best regards,
> Kenneth Holter

-- 
--
George Magklaras BSc Hons MPhil
RHCE:805008309135525

Senior Computer Systems Engineer/UNIX-Linux Systems Administrator
EMBnet Technical Management Board
The Biotechnology Centre of Oslo,
University of Oslo
http://folk.uio.no/georgios

Tel: +47-22840535

--