Date: Mon, 24 Dec 2007 22:43:16 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Andrey <andrey.kosachenko@gmail.com> Cc: freebsd-acpi@freebsd.org Subject: Re: powerd doesn't decrease CPU frequency in some cases Message-ID: <Pine.BSF.3.96.1071224223100.13064C-100000@gaia.nimnet.asn.au> In-Reply-To: <476F929E.70006@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 24 Dec 2007, Andrey wrote: > Hi, > > Thank you, Aragon. > > Actually, your patch does the same as mine (but in a different way). > Thus we have at least 2 cases so far when the challenge is appeared. > > But I'm not sure if our solutions are the best way out. > And... I believe, that it would be wonderful if Nate Lawson take a look > here and evaluate the things we are talking through. I've watched with amazement over the months seeing various problems with machines having such as 2201 and 2200, or 2001 and 2000MHz frequencies. It makes no sense to me at all that manufacturers would bother having a separate frequency just 1MHz higher. It seems ridiculous, and bogus. Just an observation .. Cheers, Ian > Aragon Gouveia wrote: > > Hi, > > > > I recently experienced the exact same behaviour as you are experiencing. > > I'm running an HP Pavilion dv2610ei. In my case, dev.cpu.0.freq_levels > > shows frequencies 2201 and 2200 (2.2 GHz Core2Duo CPU), and setting > > frequency to 2200 jumps to 2201. This was completely messing with powerd as > > it does not expect a frequency change to jump to another level. > > > > I wrote a powerd patch a while ago which adds a check condition and removes > > a frequency level if it fails to get set. It's attached. Please feel free > > to test it and report back. :) > > > > > > Regards, > > Aragon > > -- > Sincerely, > Andrey Kosachenko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.1071224223100.13064C-100000>