From: "Jason Munro" <jason@stdbev.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ACPI battery info failure after some period of time, 2.6.3-x and up
Date: Thu, 4 Mar 2004 22:08:09 -0600 [thread overview]
Message-ID: <a2dddb49576d8789a2f7092911006002@stdbev.com> (raw)
In-Reply-To: <4047756D.2050402@blue-labs.org>
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/
next prev parent reply other threads:[~2004-03-05 4:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 18:29 ACPI battery info failure after some period of time, 2.6.3-x and up David Ford
2004-03-05 4:08 ` Jason Munro [this message]
2004-03-05 4:20 ` Stuart Young
2004-03-05 4:26 ` David Ford
2004-03-05 4:43 ` Stuart Young
2004-03-05 5:02 ` Jeff Chua
2004-03-05 5:33 ` Jason Munro
2004-03-05 21:40 ` John M Flinchbaugh
2004-03-05 22:45 ` Stuart Young
2004-03-05 12:46 ` Charles Bueche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a2dddb49576d8789a2f7092911006002@stdbev.com \
--to=jason@stdbev.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.