From owner-freebsd-acpi@FreeBSD.ORG Tue Feb 8 18:29:08 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 F35A216A4CE; Tue, 8 Feb 2005 18:29:07 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A76B943D48; Tue, 8 Feb 2005 18:29:07 +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 j18IT6Wk004074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Feb 2005 10:29:06 -0800 Message-ID: <420904F2.6000305@root.org> Date: Tue, 08 Feb 2005 10:29:06 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <42068A5C.1030300@root.org> <20050207143804.7tf8xse944ck48co@netchild.homeip.net> In-Reply-To: <20050207143804.7tf8xse944ck48co@netchild.homeip.net> Content-Type: text/plain; charset=ISO-8859-15; 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: Tue, 08 Feb 2005 18:29:08 -0000 Alexander Leidinger wrote: > Nate Lawson wrote: > >> If you have throttling, please test the new configuration to be sure it >> still works as before. Final upcoming work will be manpage support and >> bugfixing as necessary. > > > Does this also affect hw.acpi.cpu.cx*? > > If yes: My desktop system only had C2 for a long time and after an > update at > the weekend I've looked at the cpufreq stuff and noticed, that it now > allows > C3 too. I've tried it and the system freezed immediatly. No way to do > anything after this, I had to reset the system. Anything I can send to you > (at the weekend) to debug this? It shouldn't affect this at all. I'll look into this eventually. -- Nate