From owner-freebsd-acpi@FreeBSD.ORG Sun Oct 23 00:29:56 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 C5A9016A41F for ; Sun, 23 Oct 2005 00:29:56 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0092943D45 for ; Sun, 23 Oct 2005 00:29:55 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j9N0UNTl031001 for ; Sat, 22 Oct 2005 20:30:23 -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 pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id j9N0Ts8x094144; Sat, 22 Oct 2005 20:29:54 -0400 Message-ID: <435AD980.3050403@root.org> Date: Sat, 22 Oct 2005 17:29:52 -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: <00a301c5d742$19c8f1a0$2603fb93@KLOBOUCEK> In-Reply-To: <00a301c5d742$19c8f1a0$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: Sun, 23 Oct 2005 00:29:56 -0000 Petr Holub wrote: >>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 > > > I'm running 6.0 RC1 and would like to stick to -stable as it is my > production machine. Anyway, thanks for explanation! > > Petr I'll try to get a workaround in before 6.0 -- Nate