From owner-freebsd-acpi@FreeBSD.ORG Sat Oct 22 18:17:13 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 861CD16A41F for ; Sat, 22 Oct 2005 18:17:13 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FF2C43D45 for ; Sat, 22 Oct 2005 18:17:13 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j9MIHvH4018658 for ; Sat, 22 Oct 2005 14:17:58 -0400 X-ORBL: [71.139.0.107] Received: from [10.0.5.50] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by pimout7-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id j9MIHAOD054308; Sat, 22 Oct 2005 14:17:11 -0400 Message-ID: <435A8223.2090703@root.org> Date: Sat, 22 Oct 2005 11:17:07 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Petr Holub References: <00a201c5d723$93901e10$2603fb93@KLOBOUCEK> In-Reply-To: <00a201c5d723$93901e10$2603fb93@KLOBOUCEK> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: powerd problem on ASUS T9400 with 6.0RC1 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: Sat, 22 Oct 2005 18:17:13 -0000 Petr Holub wrote: > Dear all, > > I've encountered a problem with powerd which seems to be specific > to ASUS T9400 laptop. Powerd crashes after arbitrary amount of > time saying that its impossible to configure (usually, but not > necessarily) the maximum processor speed: > > # powerd -v -p 200 > idle time > 90%, decreasing clock speed from 787 MHz to 700 MHz > idle time > 90%, decreasing clock speed from 787 MHz to 700 MHz > idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz > idle time < 65%, increasing clock speed from 700 MHz to 900 MHz > idle time > 90%, decreasing clock speed from 787 MHz to 700 MHz > idle time > 90%, decreasing clock speed from 700 MHz to 612 MHz > idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz > idle time < 65%, increasing clock speed from 787 MHz to 900 MHz > idle time < 65%, increasing clock speed from 787 MHz to 900 MHz > idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz > idle time < 65%, increasing clock speed from 525 MHz to 700 MHz > idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz > idle time < 65%, increasing clock speed from 612 MHz to 787 MHz > idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz > idle time < 65%, increasing clock speed from 612 MHz to 787 MHz > idle time > 90%, decreasing clock speed from 700 MHz to 612 MHz > idle time < 65%, increasing clock speed from 700 MHz to 900 MHz > powerd: error setting CPU frequency 900: Device not configured > > and dmesg shows: > acpi_perf0: Px transition to 900 failed > acpi_perf0: set freq failed, err 6 > > Interesting thing is it looks like sometimes it succeeds setting > the frequency 900 MHz and sometimes not. It's not crashing, it's exiting with an error. If you have passive cooling enabled, it can block powerd from setting a new rate (as it should). Are you running -current? If so, upgrade your powerd. I just committed some code that among other things, just gives a warning instead of exiting if it can't set the level. -- Nate