From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 20:59:14 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 D3E391065675 for ; Thu, 30 Jun 2011 20:59:14 +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 117348FC1B for ; Thu, 30 Jun 2011 20:59:13 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA24589; Thu, 30 Jun 2011 23:59:09 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QcOKK-000CQf-PZ; Thu, 30 Jun 2011 23:59:08 +0300 Message-ID: <4E0CE39C.5050307@FreeBSD.org> Date: Thu, 30 Jun 2011 23:59:08 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110626 Lightning/1.0b2 Thunderbird/3.1.11 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> In-Reply-To: <4E0CA533.5030104@agile.bc.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 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, 30 Jun 2011 20:59:15 -0000 on 30/06/2011 19:32 Ed VanderPloeg said the following: > I updated to 8-stable but am still getting ACPI error messages to console every > 10 seconds. Just for my curiosity - has anything changed with respect to est driver attachment? > 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. I've just the code in acpi_thermal driver and it doesn't have any validation for polling_rate and thus no special treatment for the value of zero. So, it passes timeout of zero to msleep() function, which does have a special meaning for zero - it means sleep forever until wakeup event. Essentially when you did sysctl hw.acpi.thermal.polling_rate=0, you made the thermal zone handling thread to sleep "forever". This can be considered a bug in FreeBSD ACPI TZ driver. The only thing that seems to be able to wake up the thread after that is a change of power profile. So switching from AC to batter or vice versa could wake up the thread and make it use a new value of polling_rate. > 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. >> -- Andriy Gapon