From owner-freebsd-current@FreeBSD.ORG Thu Jun 17 16:01:59 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 862FD1065676; Thu, 17 Jun 2010 16:01:59 +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 47B1D8FC1B; Thu, 17 Jun 2010 16:01:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o5HFrEi8069895; Thu, 17 Jun 2010 09:53:14 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 17 Jun 2010 09:53:17 -0600 (MDT) Message-Id: <20100617.095317.886429907132154868.imp@bsdimp.com> To: dougb@freebsd.org From: "M. Warner Losh" In-Reply-To: <4C187778.9060909@FreeBSD.org> References: <4C187778.9060909@FreeBSD.org> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 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: Thu, 17 Jun 2010 16:01:59 -0000 In message: <4C187778.9060909@FreeBSD.org> Doug Barton writes: : 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. You may need a simple cron entry that checks the temperature and report when it is getting close. acpi should be reporting thermal events before then that aren't 0xcc, but if not, that's the fallback that people use. Sadly, at least for one of my laptops, I've seen sudden 10-20C spikes which trigger this. I think this laptop is badly broken, and don't use it any more. Warner