Comment 6 for bug 85370

On Feisty, we don't actually run the 'powernowd', all we do is set the kernel's built-in scaling-governor. If I hadn't read the comment about "removing powernowd fixed the issue", I would have said this was likely completely unrelated to powernowd. If we don't run the '/etc/init.d/powernowd' initscript on boot, the kernel defaults to the 'conservative' governor.

That's not to say there's not something related to 'cpufreq', perhaps dropping interrupts during a state change, but I don't think it's powernowd, because powernowd simply isn't running (on Feisty).

I'm interested with any testing you can do on Feisty, but keeping the package installed and seeing whether the issue still occurs.