From owner-freebsd-current@FreeBSD.ORG Wed Jun 16 07:04:26 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE9BB106566B for ; Wed, 16 Jun 2010 07:04:26 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 826C98FC19 for ; Wed, 16 Jun 2010 07:04:26 +0000 (UTC) Received: (qmail 19420 invoked by uid 399); 16 Jun 2010 07:04:25 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 16 Jun 2010 07:04:25 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C187778.9060909@FreeBSD.org> Date: Wed, 16 Jun 2010 00:04:24 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: devd and/or ACPI not reporting a heat problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2010 07:04:26 -0000 Howdy, I thought my heat problems were over with this laptop thanks to all the great suggestions I've received about powerd, no stepping, etc. (I also propped up both the back and the front to make a nice big air pocket.) I've always been pretty religious about blowing the dust off the fans and heat sinks, but I guess it's been dustier than I thought lately because I finally "caught" my laptop doing what it's been doing for the last 2 weeks, which is (occasionally) powering down when it was unattended; and the problem was heat. Of course I've been running devd all along, and so I initially ruled out the heat problem due to this entry in devd.conf: # Notify all users before beginning emergency shutdown when we get # a _CRT or _HOT thermal event and we're going to power down the system # very soon. notify 10 { match "system" "ACPI"; match "subsystem" "Thermal"; match "notify" "0xcc"; action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; }; I'm not getting any of those notices in the logs, so I was looking other places. (I do get other ACPI-related activity from devd, such as the notice that it's going on and off AC power.) So, 2-part question, how can I make sure that devd gets the message, and how do I make sure that the notice comes _before_ the BIOS forces the system to power off. I.e., I'd like to have some sort of devd notice that comes in time to do a clean shutdown, or perhaps some other mitigation strategy prior to the BIOS taking over. Any -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/