On Tue, Mar 20, 2007 at 12:09:30AM +1100, Hamish Moffatt wrote: [] > > Why ondemand governor is bad? > > Hi, > > I have been using userspace/powernowd because it worked for me until > now. I have no preference though. I just switched to the ondemand > governor and it seems to be working so far. > > Should cpufreq-userspace be removed if it can cause general protection > faults?
That was daemon's problem, maybe some rules has changed since 2.6.16 or so, when it was updated. The userspace governor works form me, i setup laptop on minimum, and if building a kernel switch on maximum: cd /sys/devices/system/cpu/cpu0/cpufreq/ echo userspace > scaling_governor dd<scaling_min_freq>scaling_setspeed # or max here cd /tmp Another crash in your original report is related to cpu hotplug, but it seems a known problem and work-in-progress: ,-*- |Message-ID: <[EMAIL PROTECTED]> |Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/479386> | |Yet another attempt to resolve cpufreq and hotplug locking issues. `-*- I don't know how broken it may be in 2.6.18 with all debian's updates. Maybe cpu-hot-plug isn't useful for default kernel, i also don't know. Close bugreport, please, if problem will strike again you may reopen it. > Thanks for your help. Thank you. > Hamish > -- > Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> ____ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
