Date: Mon, 07 Nov 2005 09:09:55 -0800 From: Nate Lawson <nate@root.org> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: cvs-src@FreeBSD.org, Mike Silbersack <silby@silby.com>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf files src/sys/modules/acpi/acpi Makefile src/sys/dev/acpica acpi_battery.c acpi_smbat.c acpi_smbus.h acpiio.h Message-ID: <436F8A63.5020608@root.org> In-Reply-To: <868xw0d3rs.fsf@xps.des.no> References: <200511052355.jA5NtuPg026403@repoman.freebsd.org> <20051105191616.M870@odysseus.silby.com> <861x1u55qg.fsf@xps.des.no> <436E5797.7090605@root.org> <868xw0d3rs.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: > Nate Lawson <nate@root.org> writes: > >>Dag-Erling Smørgrav wrote: >> >>>Try running powerd with a 5000 ms polling interval. With the default >>>of 500 ms, it never seems to stabilize, but keeps oscillating wildly >>>in the 75-300 MHz range on my Dell Latitude D600. >> >>That is bad for performance. It can then take up to 10-15 seconds to >>promote back to 100% CPU when your system becomes busy. > > > It's not as bad for performance as me tossing the laptop out the > window in frustration because powerd keeps changing the CPU frequency > and the system freezes for just a moment every time it does. Some drivers require interrupts disabled, but it should be for a very brief time. acpi_perf usually generates an SMI so that may be slow for your BIOS. Are you getting messages on console about the change timing out? -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?436F8A63.5020608>