Comment 97 for bug 22336

Marking this critical. I can't guarantee that this will get fixed, because quite honestly, I've no way to reproduce it. What's more, I really believe this is a lack of information from hardware vendors for how to operate properly with this sort of system.

First things first, in feisty, powernowd is a one shot on boot, it doesn't stay running. Secondly, ondemand is our default governor in most cases now.

This should resolve things for most people.

For others, let's see if anyone is willing to be gracious enough to donate/loan their equipment to one of our kernel developers. We have East Coast US, Ottawa, North West US, and UK covered. We also have a UDS coming up in Seville, Spain. About the only way to get this fixed is to debug right on the machine (remote ssh access is not very useful).

Any takers? :)