On Mon, Mar 19, 2007 at 10:37:04AM +0100, Oleg Verych wrote: > On Mon, Mar 19, 2007 at 06:50:10PM +1100, Hamish Moffatt wrote: > > On Sat, Mar 17, 2007 at 07:52:37PM +0100, Oleg Verych wrote: > [] > > > Try to not use proprietary modules, powernowd daemon (use ondemand > > > driver) and reproduce that. > > > > OK, I will try all that asap (tomorrow hopefully). > > > > Two more observations since then; > > 1. It does crash under heavy load, if powernow-k8 is loaded (+ powernowd > > + cpufreq_userspace). > > This daemon seems obsolete to me: last release is more than year ago, > there's ondemand governor, no problems with brain-damage like sysfs. > > > 2. If I remove the frequency govenor stuff (stop powernowd, remove all > > modules) then it's perfectly stable. > > As i saw so many problems with sysfs (in lkml), i doubt it will get > "better" anyway. Even bug was reported against ondemand governor, and it > turned to be this daemon was running (:. > > 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? Thanks for your help. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
