Well, this bug concerns a trivial part of kernel configuration, so I'm not sure what you want me to test.
But I can assure you (just checked), latest upstream git revision b30a3f6 has CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND in its default configuration, though it is not set by default.
I also have successfully compiled upstream kernels with this option set in the past, and it worked fabulously. I'd just like to have the ondemand governor by default in *Ubuntu* kernels -- it just makes no sense to boot or e.g. check filesystems on full CPU frequency, because both is heavily I/O related. IMHO.
Well, this bug concerns a trivial part of kernel configuration, so I'm not sure what you want me to test.
But I can assure you (just checked), latest upstream git revision b30a3f6 has CONFIG_ CPU_FREQ_ DEFAULT_ GOV_ONDEMAND in its default configuration, though it is not set by default.
I also have successfully compiled upstream kernels with this option set in the past, and it worked fabulously. I'd just like to have the ondemand governor by default in *Ubuntu* kernels -- it just makes no sense to boot or e.g. check filesystems on full CPU frequency, because both is heavily I/O related. IMHO.