On Sunday 09 April 2006 05:06, Brown, Len wrote: > >Furthermore, we had some problems on multiprocessor systems in the past > >(about 1/2 year ago) with the ondemand governor. After some time the > >system was running (even some hours or even days) the machine locked up > >hard. Thus, we set the userspace governor by default on those systems > >where we never experienced such problems. At the moment I did > >only get one similar report where the root cause is not clear. > > It is important that this failure be root caused and this > doubt be put behind us. Got a bug URL? IIRC that was a powernow-k8 problem - should be fixed now. > I don't know if the amd-specific drivers would work or not. > Last I heard their latency was too high, but maybe they've > fixed that. I don't think so. > I think you'll need to keep the userspace backup scheme for systems > which have switching latency too high to load and run ondemand. That would be pretty much all AMD systems at least. But it's ugly - it would be better if ondemand worked on those too. Anyways not your problem I guess, Len. > >If so, I fully agree with you. But I do not set a specific > >policy in the powersave code explicitely for that feature. > >If the policy information > >will go into the kernel, I will use and set this one, of course. > > okay, great. > Yes, the kernel folks have known for years that this has to be done. > Hopefully progress will be made soon... I'm hoping the kernel will be able to put USB mouses to sleep soon at least. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-laptop" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
