public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
To: Stuart Young <sgy-lkml@amc.com.au>
Cc: jason@stdbev.com, linux-kernel@vger.kernel.org
Subject: Re: ACPI battery info failure after some period of time, 2.6.3-x and up
Date: Thu, 04 Mar 2004 23:26:05 -0500	[thread overview]
Message-ID: <4048015D.6070308@blue-labs.org> (raw)
In-Reply-To: <200403051520.40341.sgy-lkml@amc.com.au>

run a watch -n 1 'cat /proc.../status' and it'll happen really quick, on 
my machine it happens inside 15 minutes.  my notebook is a dell inpsiron 
8200.

Stuart Young wrote:

>On Fri, 5 Mar 2004 03:08 pm, Jason Munro wrote:
>  
>
>>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
>>    
>>
>
>Happened once to me. I actually thought my battery was dying, so I went into 
>the BIOS and did a battery cycle (full discharge). Hasn't come back since, 
>but I'd guess that was a co-incidence. Probably needed it anyway.
>
>Feb 21 18:32:10 kosh kernel:     ACPI-0279: *** Error: Looking up [NACH] in 
>namespace, AE_ALREADY_EXISTS
>Feb 21 18:32:10 kosh kernel:     ACPI-1120: *** Error: Method execution failed 
>[\_SB_.BAT0._BST] (Node c7f88ba0), AE_ALREADY_EXISTS
>
>Was running 2.6.3 (vanilla) at the time. Uptime at this point (first mention 
>in logs) was ~1 day, 1 hour & 15 mins. Probably haven't had >24 hrs uptime 
>since then. Will have this weekend (for testing).
>
>Laptop is an Asus L7300/L7200 (PIII-600 on 440MX chipset) with the latest 
>BIOS. Currently running 2.6.4-rc2 vanilla.
>  
>

  reply	other threads:[~2004-03-05  4:24 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
2004-03-05  4:20   ` Stuart Young
2004-03-05  4:26     ` David Ford [this message]
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=4048015D.6070308@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --cc=jason@stdbev.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgy-lkml@amc.com.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox