From owner-freebsd-acpi@FreeBSD.ORG Mon Feb 14 18:35:18 2005 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E45816A4CE; Mon, 14 Feb 2005 18:35:18 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 178F243D1F; Mon, 14 Feb 2005 18:35:18 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j1EIZBZj013391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Feb 2005 10:35:11 -0800 Message-ID: <4210EF5E.6020901@root.org> Date: Mon, 14 Feb 2005 10:35:10 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20050214164146.7BB8B5D07@ptavv.es.net> In-Reply-To: <20050214164146.7BB8B5D07@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: cpufreq import complete, acpi_throttling changed X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Feb 2005 18:35:18 -0000 Kevin Oberman wrote: >>Date: Sun, 13 Feb 2005 15:33:27 -0800 >>From: Nate Lawson >> >>One person reported Cx states being broken by the cpufreq import. >>(Well, actually he got a C3 state that he didn't have before but it >>didn't work.) Try setting hw.acpi.cpu.cx_lowest to C1 or something >>you're sure works. I think I've figured that one out also. When we write PSTATE_CNT to the SMI control register, his system decides to offer another Cx state in addition to providing OS control over Px states. It probably is using this as an ad-hoc way to detect that we're an advanced OS. > Things are better now, and it was not really an ACPI issue. > > For about the millionth time I remind myself: Only change one thing at a > time! > > At the same time that I started running cpufreq and acpi_perf, I also > switched from 4BSD to ULE. This is why the system started running so > much hotter! Weird. > Throttling is now working correctly and I can keep my CPU at about 175(F) > degrees or a kernel build by lowering the "frequency" from 1800 to > 1350. My dmesg shows ACPI throttling setting up fine: > cpu0: on acpi0 > acpi_perf0: on cpu0 > acpi_throttle0: on cpu0 Great! -- Nate