From owner-freebsd-acpi@FreeBSD.ORG Thu Jul 14 15:31:24 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 567061065678 for ; Thu, 14 Jul 2011 15:31:24 +0000 (UTC) (envelope-from edv@agile.bc.ca) Received: from defout.telus.net (defout.telus.net [204.209.205.30]) by mx1.freebsd.org (Postfix) with ESMTP id B6AE28FC17 for ; Thu, 14 Jul 2011 15:31:23 +0000 (UTC) Received: from edmwcm02 ([204.209.205.30]) by priv-edmwes04.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20110714153117.HVJS24872.priv-edmwes04.telusplanet.net@edmwcm02> for ; Thu, 14 Jul 2011 09:31:17 -0600 Received: from [192.168.0.253] ([75.155.141.59]) by edmwcm02 with bizsmtp id 7rXH1h00d1H5dnv01rXHPE; Thu, 14 Jul 2011 09:31:17 -0600 X-Authority-Analysis: v=1.1 cv=PaS+rgWywBuMo+rlDu2yD6cS+QI8Ou1WsTUJ6HmG/7s= c=1 sm=2 a=00GrbmtOa5AA:10 a=lp1F1aYoXqwA:10 a=8nJEP1OIZ-IA:10 a=wFaEK3txAAAA:8 a=tRTBw__SEBnbI5m3VfYA:9 a=wPNLvfGTeEIA:10 a=5Ut32mfbI-AA:10 X-Telus-Outbound-IP: 75.155.141.59 Message-ID: <4E1F0BC1.4030802@agile.bc.ca> Date: Thu, 14 Jul 2011 08:31:13 -0700 From: Ed VanderPloeg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Andriy Gapon References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> <4E0CA533.5030104@agile.bc.ca> <4E0CE39C.5050307@FreeBSD.org> <4E0D4A15.6000904@agile.bc.ca> <4E0D5EA0.1020704@FreeBSD.org> <4E0E7F91.2050408@agile.bc.ca> <4E117FE8.9030703@FreeBSD.org> In-Reply-To: <4E117FE8.9030703@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure 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, 14 Jul 2011 15:31:24 -0000 Could the system overheat, or get incorrectly shut down when acpi fails to get the current temperature? What is the best way to work around this problem? Setting a very high polling rate or disabling it inside loader.conf: debug.acpi.disable="thermal" In 2008 Kevin Foo thought it might not be safe to disable it: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2008-01/msg00791.html Or do I need to boot with ACPI disabled until a BIOS fix is available? Ed On 2011-07-04 1:55 AM, Andriy Gapon wrote: > on 02/07/2011 05:16 Ed VanderPloeg said the following: >> >> # egrep '(^| )est' dmesg.8-release >> est0: on cpu0 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 60f0c270600060f >> device_attach: est0 attach returned 6 >> est1: on cpu1 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 60f0c270600060f >> device_attach: est1 attach returned 6 >> >> # egrep '(^| )est' dmesg.8-stable >> est0: on cpu0 >> est1: on cpu1 > > So this was improved. Thanks! >