Comment 18 for bug 432706

I believe I am also experiencing the same bug.
I started trying to get CPU scaling enabled on my HP DL380 G3 (2x Xeon 2.4Ghz HT) a couple of days back and wasn't having much luck using powernowd or the command line to manually set governer.

I ended up using cpufreqd as this at least seemed to allow scaling on one of the 2 CPU in the machine. I went back in and checked my dmesg and I'm getting the ondemand governor failed, too long transition latency of HW, fallback to performance governor error messages (mentioning both ondemand and conservative).

I'm using the p4-clockmod module for this and the output of cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency is also 10000001 as mentioned by Anno previously.