From: Alexey Starikovskiy <aystarik@gmail.com>
To: Christian Iversen <chrivers@iversen-net.dk>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI strangeness - battery jumping to low capacity and back
Date: Mon, 16 Jul 2007 19:25:06 +0400 [thread overview]
Message-ID: <469B8DD2.1040304@gmail.com> (raw)
In-Reply-To: <469B4E8A.3050809@iversen-net.dk>
Hi Christian,
First, it is better if you open a bug in bugzilla.kernel.org against
ACPI/Battery and attach all your files there, so they will not be lost.
Second, please try latest stable kernel from kernel.org, not Ubuntu one,
as they seem to be not very careful with ACPI.
Regards,
Alex.
Christian Iversen wrote:
>
> Hi $ALL
>
> My notebook is behaving somewhat oddly. The KDE battery indicator
> usually shows the right amount of battery power left, although every now
> and then, it jumps to a value in the range 0-10%, and then jumps back.
> This is quite annoying, because it gives of all sorts of warnings about
> imminent power failure.
>
> I'm running kubuntu 7.04 with 2.6.20-15-generic from standard packages,
> on a Zepto 4200 (rebranded Compal CL56)
>
> It _seems_ -- I'm not quite sure about the causality of this -- that the
> following error messages turn up in dmesg when the jump happens:
>
> ...
> [577843.068000] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.LPC0.BAT1._BST] (Node df853608), AE_NOT_FOUND
> [577843.068000] ACPI Exception (acpi_battery-0207): AE_NOT_FOUND,
> Evaluating _BST [20060707]
> [577873.068000] ACPI Error (psargs-0355): [PBST] Namespace lookup
> failure, AE_NOT_FOUND
> [577873.068000] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.LPC0.BAT1._BST] (Node df853608), AE_NOT_FOUND
> [577873.068000] ACPI Exception (acpi_battery-0207): AE_NOT_FOUND,
> Evaluating _BST [20060707]
> [577903.080000] ACPI Error (psargs-0355): [PBST] Namespace lookup
> failure, AE_NOT_FOUND
> [577903.080000] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.LPC0.BAT1._BST] (Node df853608), AE_NOT_FOUND
> [577903.080000] ACPI Exception (acpi_battery-0207): AE_NOT_FOUND,
> Evaluating _BST [20060707]
> [577933.076000] ACPI Error (psargs-0355): [PBST] Namespace lookup
> failure, AE_NOT_FOUND
> [577933.076000] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.LPC0.BAT1._BST] (Node df853608), AE_NOT_FOUND
> [577933.076000] ACPI Exception (acpi_battery-0207): AE_NOT_FOUND,
> Evaluating _BST [20060707]
> [577963.068000] ACPI Error (psargs-0355): [PBST] Namespace lookup
> failure, AE_NOT_FOUND
> [577963.068000] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.LPC0.BAT1._BST] (Node df853608), AE_NOT_FOUND
> [577963.068000] ACPI Exception (acpi_battery-0207): AE_NOT_FOUND,
> Evaluating _BST [20060707]
> ...
>
> Maybe it has nothing to do with it? It seems to be battery-related, at
> least.
>
> Is there something else I can do to help debug the cause of these error
> messages and/or the battery problem?
>
> I've attached the output of dmidecode and acpidump, in case it's useful.
>
next prev parent reply other threads:[~2007-07-16 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 10:55 ACPI strangeness - battery jumping to low capacity and back Christian Iversen
2007-07-16 15:25 ` Alexey Starikovskiy [this message]
2007-07-17 8:41 ` Christian Iversen
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=469B8DD2.1040304@gmail.com \
--to=aystarik@gmail.com \
--cc=chrivers@iversen-net.dk \
--cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox