Message-ID: <a2dddb49576d8789a2f7092911006002@stdbev.com>
Date: Thu,  4 Mar 2004 22:08:09 -0600
From: "Jason Munro" <jason@stdbev.com>
Subject: Re: ACPI battery info failure after some period of time, 2.6.3-x and up
To: linux-kernel@vger.kernel.org
Reply-to: <jason@stdbev.com>
In-Reply-To: <4047756D.2050402@blue-labs.org>
References: <4047756D.2050402@blue-labs.org>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1458
Lines: 40

On 12:29 pm Mar 4 David Ford <david+challenge-response@blue-labs.org> wrote:
> powerix root # cat /proc/acpi/battery/BAT0/state
> present:                 yes
> ERROR: Unable to read battery status
>
> powerix root # dmesg -c
>     ACPI-0279: *** Error: Looking up [BST0] in namespace,
> AE_ALREADY_EXISTS     ACPI-1120: *** Error: Method execution failed
> [\_SB_.BAT0._BST] (Node e7bd7680), AE_ALREADY_EXISTS
>
> powerix root # uname -r
> 2.6.4-rc1
>
> This has been going on since about 2.6.3-rc something.  Some while
> after reading the /proc files, the ability to read the battery
> information gets munged.

Same here on a Toshiba 1410-s173 noteboook:

[logger] ACPI group battery / action battery is not defined
[kernel] ACPI-0279: *** Error: Looking up [BUFF] in namespace, 
         AE_ALREADY_EXISTS

I don't think it's happened in less than 24 hours of uptime, during which
everything is good. I have been using suspend to ram daily if that matters
(echo 3 > /proc/acpi/sleep).

Linux version 2.6.3-wolk1.0 (root@jackass) (gcc version 3.3.3 20040217
(Gentoo Linux 3.3.3, propolice-3.3-7)) #1 Thu Feb 26 16:18:24 CST 2004

\__ Jason Munro
 \__ jason@stdbev.com
  \__ http://hastymail.sourceforge.net/


-
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/