From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 18 12:32:47 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 3D542106566B for ; Mon, 18 Jul 2011 12:32:47 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 848508FC16 for ; Mon, 18 Jul 2011 12:32:46 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA22410; Mon, 18 Jul 2011 15:32:41 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E2427E9.3000105@FreeBSD.org> Date: Mon, 18 Jul 2011 15:32:41 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Ed VanderPloeg 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> <4E1F0BC1.4030802@agile.bc.ca> In-Reply-To: <4E1F0BC1.4030802@agile.bc.ca> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii 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: Mon, 18 Jul 2011 12:32:47 -0000 on 14/07/2011 18:31 Ed VanderPloeg said the following: > Could the system overheat, or get incorrectly shut down when acpi fails to get the > current temperature? I am not sure. There is no explicit error handling in acpi thermal driver, tz_temperature would probably always stay at zero (Kelvin) and it's not clear what the driver ends up doing in this case. You can probably simply observe your troublesome system and see which ACx state is used and how fast your fan rotates. > What is the best way to work around this problem? Setting a very high polling > rate or disabling it inside loader.conf: Interval, not rate. > debug.acpi.disable="thermal" This means that fan speed will stay whatever it was at boot time. And there won't be any passive cooling via CPU throttling. > 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 There is no justification, only an opinion in that post. You can decide and/or try for yourself. > Or do I need to boot with ACPI disabled until a BIOS fix is available? You can try this, but I am not sure if your system would even boot successfully. A lot of modern HW just plain doesn't work without ACPI. > 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! >> -- Andriy Gapon