busy IPMI kernel thread

[Curtis Doty]

Apoligies if this list is supposed to be solely about distribution 
politics. But I've an operational curiosity...

Does anyone know why the ipmi_si module and kipmi0 thread are so busy on a 
totally quiet pristine Fedora 10 install?

I've installed minimialist and done nothing but a few tests. But they're 
already acumulating *way* to many clicks.

# lsmod |grep ipmi
ipmi_si                47564  0
ipmi_msghandler        39288  1 ipmi_si

# ps -fp `pgrep ipmi`
UID        PID  PPID  C STIME TTY          TIME CMD
root      1492     2  0 Nov30 ?        00:04:12 [kipmi0]

# egrep 'CPU|ipmi' /proc/interrupts
            CPU0       CPU1       CPU2       CPU3       CPU4       CPU5       CPU6       CPU7
  21:       9215        407     334886        114       6969        406     334900        109   IO-APIC-fasteoi   ipmi_si

Hardware is an HP ProLiant G5 with no vendor crud installed.

../C

[Dan Horák]

Curtis Doty píše v Po 01. 12. 2008 v 20:09 -0800:
> Apoligies if this list is supposed to be solely about distribution 
> politics. But I've an operational curiosity...

This is the place for technical discussion too, only the auditorium is
rather small now.
> Does anyone know why the ipmi_si module and kipmi0 thread are so busy on a 
> totally quiet pristine Fedora 10 install?
>
> I've installed minimialist and done nothing but a few tests. But they're 
> already acumulating *way* to many clicks.
>
> # lsmod |grep ipmi
> ipmi_si                47564  0
> ipmi_msghandler        39288  1 ipmi_si
>
> # ps -fp `pgrep ipmi`
> UID        PID  PPID  C STIME TTY          TIME CMD
> root      1492     2  0 Nov30 ?        00:04:12 [kipmi0]
>
> # egrep 'CPU|ipmi' /proc/interrupts
>             CPU0       CPU1       CPU2       CPU3       CPU4       CPU5       CPU6       CPU7
>   21:       9215        407     334886        114       6969        406     334900        109   IO-APIC-fasteoi   ipmi_si
>
> Hardware is an HP ProLiant G5 with no vendor crud installed.

When you decide to fill a bug for this behavior, make it block the
FedoraServerTracker bug for easier tracking.

Dan