From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 2 14:24:32 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85AF4106566C for ; Thu, 2 Apr 2009 14:24:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 555C58FC0A for ; Thu, 2 Apr 2009 14:24:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net [98.109.39.197]) by cyrus.watson.org (Postfix) with ESMTPSA id D79A746B58; Thu, 2 Apr 2009 10:24:31 -0400 (EDT) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n32EOPT0048814; Thu, 2 Apr 2009 10:24:25 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Thu, 2 Apr 2009 09:08:00 -0400 User-Agent: KMail/1.9.7 References: <20090402033543.43DDD1CC0B@ptavv.es.net> In-Reply-To: <20090402033543.43DDD1CC0B@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904020908.00723.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 02 Apr 2009 10:24:26 -0400 (EDT) X-Virus-Scanned: ClamAV 0.94.2/9198/Thu Apr 2 02:50:41 2009 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: Re: Wrong dev.cpu.0.freq_levels values X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2009 14:24:32 -0000 On Wednesday 01 April 2009 11:35:43 pm Kevin Oberman wrote: > > Date: Wed, 01 Apr 2009 23:16:13 -0400 > > From: Pierre-Luc Drouin > > Sender: owner-freebsd-acpi@freebsd.org > > > > I tried disabling both p4tcc and acpi_throttle by putting the following > > in /boot/device.hints: > > hint.p4tcc.0.disabled="1" > > hint.acpi_throttle.0.disabled="1" > > > > It reduced the number of levels, but I still don't have a level 2000 as > > I used to get: > > dev.cpu.0.freq: 1500 > > dev.cpu.0.freq_levels: 1500/-1 1200/-1 1000/-1 800/-1 600/-1 > > dev.est.0.%desc: Enhanced SpeedStep Frequency Control > > dev.est.0.freq_settings: 1500/-1 1200/-1 1000/-1 800/-1 600/-1 > > > > Pierre-Luc Drouin > > > > Nate Lawson wrote: > > > Pierre-Luc Drouin wrote: > > > > > >> Hello, > > >> > > >> I have noticed that FreeBSD gets the wrong CPU frequency levels for my > > >> Pentium M 2GHz. It used to work correctly with older versions of > > >> FreeBSD, but I noticed that this was not working properly when I > > >> installed 7.1 and this is still not working with -stable: > > >> > > >> > > > > > > > > >> dev.cpu.0.freq: 1500 > > >> dev.cpu.0.freq_levels: 1500/-1 1312/-1 1200/-1 1050/-1 1000/-1 875/-1 > > >> 800/-1 700/-1 600/-1 525/-1 450/-1 375/-1 300/-1 225/-1 150/-1 75/-1 > > >> dev.est.0.%desc: Enhanced SpeedStep Frequency Control > > >> dev.est.0.freq_settings: 1500/-1 1200/-1 1000/-1 800/-1 600/-1 > > >> > > >> Is there a way to fix this? > > >> > > > > > > There's nothing wrong. You just got more levels using p4tcc (another > > > cpufreq device). So use it as-is, or disable the p4tcc driver and > > > acpi_throttle drivers. > > > > > There is a problem, of course. I had the same issue with my 2GHz Pentium > M. It was easy to fix, but totally counter-intuitive. > > Build your kernel without "device cpufreq" and it will all work > fine. Here is what I see without CPUFREQ: > dev.cpu.0.freq_levels: 2000/27000 1750/23625 1600/22600 1400/19775 1333/19666 1166/17207 1066/16733 932/14641 800/13800 700/12075 600/10350 500/8625 400/6900 300/5175 200/3450 100/1725 Hmm, that means one of the cpufreq drivers is busted I think. Can you try disabling all of them to see which one is the problem (est perhaps?) Also, can you show the 'devinfo' output for your cpu0 device (and its child devices) in the cpufreq and non-cpufreq cases? -- John Baldwin