Date: Sun, 28 Jun 2009 23:42:48 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Kevin Oberman <oberman@es.net> Cc: freebsd-acpi@freebsd.org Subject: Re: acpi/cpu scaling probs? Dell D820 FreeBSD current Message-ID: <4A47D5C8.4090701@FreeBSD.org> In-Reply-To: <20090628203245.B10F01CC2E@ptavv.es.net> References: <20090628203245.B10F01CC2E@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman wrote: >> Date: Sun, 28 Jun 2009 21:55:48 +0300 >> From: Alexander Motin <mav@FreeBSD.org> >> Sender: owner-freebsd-acpi@freebsd.org >> >> Ron Freidel wrote: >>> I hope I am posting to the correct list... >>> >>> I have updated to FreeBSD current to try out acpi sleep, which works great >>> by the way, and the improvements to wifi and the addition of sleep are >>> enough to keep current on the laptop. >>> >>> Here's the problem, the cpu is maxed out, no scaling at all. >>> >>> Here's the output of powerd -v >>> <snip> >>> load 108%, current freq 2000 MHz ( 0), wanted freq 4000 MHz >>> load 109%, current freq 2000 MHz ( 0), wanted freq 4000 MHz >>> load 102%, current freq 2000 MHz ( 0), wanted freq 4000 MHz >>> load 124%, current freq 2000 MHz ( 0), wanted freq 4000 MHz >>> load 108%, current freq 2000 MHz ( 0), wanted freq 4000 MHz >>> <snip> >> ^^^ >> This is the reason. powerd sees that one of your CPUs is constantly >> busy. You should investigate why and what that CPU does. > > Agreed, but that still does not explain why it keeps trying to set the > clock to 4 GHz on a 2 GHz system. Not too surprising that it does not > work. :-) It is not a bug, but feature. It is specific of the "hiadaptive" mode. It means that CPU is too busy now and should not drop frequency immediately after load drops to not loose system interactivity and performance. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A47D5C8.4090701>