Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752688AbZI2OH1 (ORCPT ); Tue, 29 Sep 2009 10:07:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752628AbZI2OHZ (ORCPT ); Tue, 29 Sep 2009 10:07:25 -0400 Received: from mail-fx0-f218.google.com ([209.85.220.218]:47524 "EHLO mail-fx0-f218.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752629AbZI2OHY (ORCPT ); Tue, 29 Sep 2009 10:07:24 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XAxIGBb5IlYObELmROOS8TiM1wI6m1c51AHlmBJHkvGqfTh/uKpM2AY+eoAB4FvyFf lKL6+wnYI4cdE0hpFfRSfEnM1krDzzChQKohZae3mUW8P0Lk7/NGkDR49lI7/KtQP8iZ FJgC8DEe2Gv6cjVEaaMprff76K78sAXxKRsgQ= MIME-Version: 1.0 In-Reply-To: <51f3faa70909282134o1d60efekeded09f09b192df6@mail.gmail.com> References: <20090923191240.GA15198@dreamland.darkstar.lan> <51f3faa70909232018v7e621190m84deb648b08d2135@mail.gmail.com> <20090928131700.GA19243@nb-core2.darkstar.lan> <51f3faa70909281920x2782d8dfm1835ab24779abfa3@mail.gmail.com> <51f3faa70909282134o1d60efekeded09f09b192df6@mail.gmail.com> Date: Tue, 29 Sep 2009 16:07:26 +0200 Message-ID: <68676e00909290707u70d192f2j2f2d4dd07bd07234@mail.gmail.com> Subject: Re: [PATCH] asus_atk0110: add support for Asus P7P55D From: Luca Tettamanti To: Robert Hancock Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org, Jean Delvare Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2759 Lines: 56 On Tue, Sep 29, 2009 at 6:34 AM, Robert Hancock wrote: > On Mon, Sep 28, 2009 at 8:20 PM, Robert Hancock wrote: >> On Mon, Sep 28, 2009 at 7:17 AM, Luca Tettamanti wrote: >>> On Wed, Sep 23, 2009 at 09:18:45PM -0600, Robert Hancock wrote: >>>> On Wed, Sep 23, 2009 at 1:12 PM, Luca Tettamanti wrote: >>>> > With P7P55D (and newer) boards Asus extended the output buffer (ASBF) >>>> > making the driver unable to read the data from the sensors. >>>> > Change the driver to use dynamic buffers (allocated by ACPI core); the >>>> > return value is cached, so the number of memory allocations is very low. >>>> > >>>> > Signed-off-by: Luca Tettamanti >>>> > Tested-by: Robert Hancock >>>> >>>> I just noticed a problem (either with this patch or some other issue >>>> with the driver on this board): The readings don't seem to be >>>> updating, I get the same values all the time. (Just now I started >>>> compiling a kernel and coretemp reports temperatures in the 60 degree >>>> plus range but atk0110-acpi still reports 35 degrees as it did >>>> before..) >>> >>> Hi Robert, >>> I have a new patch for you :) >>> It contains the previous changes to handle the bigger ASBF buffer plus a new >>> method to enable the EC as suggested by Asus. Be sure to compile with >>> HWMON_DEBUG_CHIP enabled. >> >> Excellent.. seems to work now and give actually updating sensor readings :-) > > Have seen a couple of these though, looks like about once an hour: > > ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] > (20090903/evregion-424) > ACPI Error (psparse-0537): Method parse/execution failed > [\_SB_.PCI0.SBRG.ASOC.GIT6] (Node ffff88013ba778c0), AE_TIME > ACPI Error (psparse-0537): Method parse/execution failed > [\_SB_.PCI0.SBRG.ASOC.GITM] (Node ffff88013ba6ea40), AE_TIME > ATK0110 ATK0110:00: atk_read_value_new: ACPI exception: AE_TIME > > Maybe sometimes the embedded controller takes longer than the timeout > to process, or something? Is there a message like "input buffer is not empty" before that? >> By the way, if you have any firmware-type contacts at Asus that know >> about these boards, you might want to point them at this problem, the >> BIOS DMAR tables point to invalid locations when Intel VT-d is >> enabled. So far haven't gotten any useful response from tech support.. I don't have any inside contact, sorry (and I agree with dwmw2 :P) L -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/