From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 16:33:07 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 DED6B1065675 for ; Thu, 30 Jun 2011 16:33:06 +0000 (UTC) (envelope-from edv@agile.bc.ca) Received: from defout.telus.net (defout.telus.net [204.209.205.13]) by mx1.freebsd.org (Postfix) with ESMTP id 640658FC1C for ; Thu, 30 Jun 2011 16:33:05 +0000 (UTC) Received: from edmwcm04 ([204.209.205.13]) by priv-edmwes04.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20110630163259.BAYT24872.priv-edmwes04.telusplanet.net@edmwcm04> for ; Thu, 30 Jun 2011 10:32:59 -0600 Received: from [192.168.0.253] ([75.155.136.54]) by edmwcm04 with bizsmtp id 2GYz1h00z1Abl5F01GYz7l; Thu, 30 Jun 2011 10:32:59 -0600 X-Telus-Outbound-IP: 75.155.136.54 X-Authority-Analysis: v=1.1 cv=QUfQBVzlX4/ya68PAJjJGj5hWUIyJvqu6OBFlX9+M7Y= c=1 sm=2 a=00GrbmtOa5AA:10 a=lp1F1aYoXqwA:10 a=8nJEP1OIZ-IA:10 a=HUAmJIpXAAAA:8 a=wVjY19UYuB-NpeheeoMA:9 a=wNmF7C-BXVrkVKAMYlUA:7 a=wPNLvfGTeEIA:10 Message-ID: <4E0CA533.5030104@agile.bc.ca> Date: Thu, 30 Jun 2011 09:32:51 -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: freebsd-acpi@FreeBSD.org References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> In-Reply-To: <4E0B80BE.6080605@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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, 30 Jun 2011 16:33:07 -0000 I updated to 8-stable but am still getting ACPI error messages to console every 10 seconds. What happens when sysctl hw.acpi.thermal.polling_rate=0? Does this disable polling? I noticed that when I set it to zero, the error messages seem to stop, but then setting it to a non-zero value never brings the messages back again. Ed On 2011-06-29 12:45 PM, Andriy Gapon wrote: > on 29/06/2011 21:01 Ed VanderPloeg said the following: >> On 2011-06-29 2:38 AM, Andriy Gapon wrote: >>> on 29/06/2011 01:07 Ed VanderPloeg said the following: >>>> I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which >>>> uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm >>>> now getting the following (verbose) console message during boot and every 10 >>>> seconds thereafter: >>>> >>>> ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND (20101013/psargs-464) >>>> ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), >>>> AE_NOT_FOUND (20101013/psparse-633) >>>> acpi_tz0: error fetching current temperature -- AE_NOT_FOUND >>> >>> The problem is that RTMP is defined as an external object: >>> External (RTMP, IntObj) >>> so it's supposed to come from an additional table, but apparently either no >>> additional table defines it or a necessary additional table is not loaded. >>> This could be either a BIOS problem or... something else :) >> >> Aaeon tech support has now stated that the errors are from a faulty BIOS, and >> that AWARD will eventually release an update to fix this. > > OK. > >>>> The unit seems to run very warm which makes me wonder if this problem is >>>> preventing lower power states, if such things are related. >>>> >>>> I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from >>>> acpidump. They are zipped up over here: >>>> >>>> http://www.agilecontrols.com/post/aec6831_acpi.zip >>> >>> Try either recent stable/8 or head (aka CURRENT) and see if it helps. They >>> contain a change that may be a work-around for a BIOS (ACPI tables) like yours. >> >> I'll give stable/8 a try. >> >> Does this error indicate something potentially harmful, or if it is benign? I >> can silence the messages easy enough until a BIOS update comes out. > > > Actually I was speaking about potentially making est driver attach on your > system. I also suspected that RTMP might have gotten loaded from the same > dynamic table that is related to est attachment issue, but apparently that was > not going to happen. >