Date: Mon, 8 Mar 2010 18:40:28 +0200 From: Dan Naumov <dan.naumov@gmail.com> To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Jeremy Chadwick <freebsd@jdc.parodius.com>, freebsd-questions@freebsd.org Subject: Re: powerd on 8.0, is it considered safe? Message-ID: <cf9b1ee01003080840u2d570deeu3f348f0a8014096c@mail.gmail.com> In-Reply-To: <cf9b1ee01003080429n6398dd32ke5247e5833a338d4@mail.gmail.com> References: <cf9b1ee01003080429n6398dd32ke5247e5833a338d4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
OK, now I feel a bit stupid. The second half of my PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=144551 (anything related to powerd behaviour) can be ignored. For testing purposes, I started powerd in the foreground and observed it's behaviour. It works exactly as advertised and apparently the very act of issuing a "sysctl -a | grep dev.cpu.0.freq" command uses up a high % of CPU time for a fraction of a second, resulting in confusing output, I was always getting the highest cpu frequency state as the output. Testing powerd in foreground however, shows correct behaviour, CPU is downclocked both before and after issuing that command :) Still doesn't explain why the system boots up at 1249 Mhz, but that's not that big of an issue at this point now I see that powerd is behaving correctly. - Sincerely, Dan Naumov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cf9b1ee01003080840u2d570deeu3f348f0a8014096c>