From owner-freebsd-acpi@FreeBSD.ORG Thu Aug 2 22:41:41 2007 Return-Path: Delivered-To: acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B60316A417; Thu, 2 Aug 2007 22:41:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 3660213C49D; Thu, 2 Aug 2007 22:41:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l72Mf9re064933; Thu, 2 Aug 2007 16:41:09 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 02 Aug 2007 16:41:16 -0600 (MDT) Message-Id: <20070802.164116.-1894448262.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <46B25AD0.70706@root.org> References: <46B20F91.5080709@root.org> <20070802.115713.71149193.imp@bsdimp.com> <46B25AD0.70706@root.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 02 Aug 2007 16:41:10 -0600 (MDT) Cc: acpi@freebsd.org, freebsd-hackers@freebsd.org, ume@freebsd.org, gahr@gahr.ch Subject: Re: [patch] enhance powerd(8) to handle max temperature 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 Aug 2007 22:41:41 -0000 In message: <46B25AD0.70706@root.org> Nate Lawson writes: : Warner Losh wrote: : > From: Nate Lawson : > Subject: Re: [patch] enhance powerd(8) to handle max temperature : > Date: Thu, 02 Aug 2007 10:08:33 -0700 : > : >> M. Warner Losh wrote: : >>> I keep getting the system shutting down on my HP by FreeBSD because : >>> the temperature exceeds the _CRT value. Maybe there's something wrong : >>> with my values, since it happens a lot: : >>> : >>> hw.acpi.thermal.min_runtime: 0 : >>> hw.acpi.thermal.polling_rate: 10 : >>> hw.acpi.thermal.user_override: 0 : >>> hw.acpi.thermal.tz0.temperature: 0.0C : >>> hw.acpi.thermal.tz0.active: -1 : >>> hw.acpi.thermal.tz0.passive_cooling: 1 : >>> hw.acpi.thermal.tz0.thermal_flags: 0 : >>> hw.acpi.thermal.tz0._PSV: 90.0C : >>> hw.acpi.thermal.tz0._HOT: -1 : >>> hw.acpi.thermal.tz0._CRT: 94.0C : >>> hw.acpi.thermal.tz0._ACx: 40.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 : >>> : >>> Note: temperature is always 0.0C. : >>> : >>> What can I do to help my situation, if I really want the kernel doing : >>> the cooling? : >> Your embedded controller is timing out. Thus you're getting a bogus : >> value for _TMP. : >> : >> Those settings for _CRT appear correct. It's the "measured" temperature : >> that is wrong. : > : > So how do I track down the problem? I'm tired of the system just : > shutting down when I'm building OOO or even something simpler like : > doing a buildworld... : : You do what's #1 on my list, which is rewrite the EC driver event model : (yet again) and figure out if it's possible to automatically detect : which workarounds are needed. Linux requires you to specify boot-time : flags to select polled or event-driven work. Hmmm. OK. Warner