battery state not reported correctly

Bug #116185 reported by mehturt
14
Affects Status Importance Assigned to Milestone
Linux
Fix Released
High
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
High
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

Sometimes the battery state is not reported correctly.
The syslog contains errors, such as:

May 22 13:35:07 pyty2 kernel: [21427.476000] ACPI Error (psargs-0355): [PBST] Namespace lookup failure, AE_NOT_FOUND
May 22 13:35:07 pyty2 kernel: [21427.476000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPCB.BAT1._BST] (Node c19866a8), AE_NOT_FOUND
May 22 13:35:07 pyty2 kernel: [21427.476000] ACPI Exception (acpi_battery-0207): AE_NOT_FOUND, Evaluating _BST [20060707]

The KLaptop indicator displays an empty battery, but after 20-30 seconds it shows the correct battery status again. When this happens, no info is written to syslog..

The syslog errors then appear periodically, each minute or so.

Tags: cft-2.6.27
Revision history for this message
mehturt (mehturt) wrote :

Running Ubuntu (Kubuntu) Fiesty,
Linux pyty2 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Revision history for this message
mehturt (mehturt) wrote :

Maybe another info - the laptop is Toshiba Sattelite M100-222.
I can provide more info if requested.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the contents of '/proc/acpi/dsdt' as an attachment to your bug report? Thanks in advance.

Revision history for this message
mehturt (mehturt) wrote :

Here it is. Hope it helps.

Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Flávio Martins (flavioxmartins) wrote :

Same problems here running latest Gutsy kernel.
I'm attaching my dsdt. I've fixed the dsdt bugs iasl reported, but in the end g-p-m still locks up, and the proc state file for the battery cannot be read.
I have to add that the problem for me seems to be the AC connect/disconnect action, the change between ac power and battery is what is causing the problem.
Also a user can't end a session because g-p-m is locked. Might as well poke g-p-m to gracefully quit polling the battery if the kernel messes up.

Changed in linux-source-2.6.22:
status: New → Confirmed
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Flávio Martins (flavioxmartins) wrote :

Using a laptop with this bug is quite a nightmare.
This is also a regression.

Changed in linux-source-2.6.22:
importance: Undecided → Medium
Revision history for this message
Flávio Martins (flavioxmartins) wrote :

Setting as high importance since this seems to affect a high number of machines.

Changed in linux-source-2.6.22:
importance: Medium → High
Changed in linux-source-2.6.20:
importance: Medium → High
Changed in linux:
status: Unknown → Confirmed
Revision history for this message
Stas Zytkiewicz (stas-zytkiewicz) wrote :

A have a similiar problem on a Asus A2H laptop running Gutsy but without the syslog messages and g-p-m lock ups.

stas@mobi:~$ uname -a
Linux mobi 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Laptop on DC:

stas@mobi:~$ acpi -V
     Battery 1: discharging, 99%, 68:57:00 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

After 30 minutes or so:

stas@mobi:~$ acpi -V
     Battery 1: discharging, 99%, 207:42:00 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

Some time later:
stas@mobi:~$ acpi -V
     Battery 1: discharging, 99%, 277:08:00 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

The battery is charging, remaining time increases, but acpi thinks it's discharging.
g-p-m is reporting that the battery is discharging but reports that "the battery discharge time
is unkown" .
I can't find any errors in syslog or dmesg.

Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi All,

Care to test the latest Hardy Alpaha release. The reason I ask is I believe this issue is resolved with the newer kernel release.
The following upstream bug report:
 http://bugzilla.kernel.org/show_bug.cgi?id=9730 exhibitted similar
 errors. The patch which resolved that issue was shipped in upstream's
 linux-2.6.24-rc7-git5. The Ubuntu kernel then pulled in this patch for
 the 2.6.24-5.8 Ubuntu kernel release. The easiest way to test the new kernel will probably be to download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ .

Also note that we will keep this report open against the actively developed kernel bug against 2.6.20 and 2.6.22 this will be closed. Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Changed in linux-source-2.6.22:
status: Confirmed → Won't Fix
Revision history for this message
Stas Zytkiewicz (stas-zytkiewicz) wrote : Re: [Bug 116185] Re: battery state not reported correctly

On Wed, Mar 5, 2008 at 4:11 PM, Leann Ogasawara <email address hidden> wrote:
> Hi All,
>
> Care to test the latest Hardy Alpaha release. The reason I ask is I believe this issue is resolved with the newer kernel release.
I tested the hardy alpha6 live cd but the issue isn't resolved.
The bug can be reproduced by unplugging the AC and replugging it
again, then after
one minute acpi+g-p-m thinks the battery is unplugged again.

Here's the what acpi reported:
(laptop on AC system up and running, g-p-m gives the unplugged warning)
ubuntu@ubuntu:~$ acpi -V
     Battery 1: discharging, 98%, 02:06:43 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: off-line

(laptop after unplugging AC)
ubuntu@ubuntu:~$ acpi -V
     Battery 1: discharging, 98%, 04:25:27 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: off-line

( and replugging it again)
ubuntu@ubuntu:~$ acpi -V
     Battery 1: charging, 98%, 00:33:00 until charged
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

Then after one +- one minute g-p-m gave an popup telling the laptop
was disconnected.(Which wasn't the case)
ubuntu@ubuntu:~$ acpi -V
     Battery 1: discharging, 98%, 18:23:56 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

The remaining outputs shows that the battery is charging as the remaining times
increases.

ubuntu@ubuntu:~$ acpi -V
     Battery 1: discharging, 98%, 25:42:22 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

ubuntu@ubuntu:~$ acpi -V
     Battery 1: discharging, 98%, 27:48:38 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

ubuntu@ubuntu:~$ acpi -V
     Battery 1: discharging, 98%, 31:56:44 remaining
     Thermal 1: ok, 53.0 degrees C
  AC Adapter 1: on-line

I can't find anything useful in the logs but if you need more info I'm
happy to provide it.

Stas

--
Free-source educational programs for schools
http://www.schoolsplay.org and http://wiki.laptop.org/go/Schoolsplay
http://gvr.sf.net and http://wiki.laptop.org/go/Guido_van_Robot

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Stas. Care to actually open a new bug report? It would seem that you have a slightly different bug and are also on different hardware than the original bug reporter. We can easily mark bugs as duplicates later on if necessary. In the new bug report if you could include exactly what you wrote in https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/116185/comments/10 that would be great. Also, could you please include the required debugging information outlined here: https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks!

Revision history for this message
Stas Zytkiewicz (stas-zytkiewicz) wrote :

On Tue, Mar 11, 2008 at 6:01 PM, Leann Ogasawara <email address hidden> wrote:
> Thanks Stas. Care to actually open a new bug report? It would seem
Done.
https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.11/+bug/201318

Stas

--
Free-source educational programs for schools
http://www.schoolsplay.org and http://wiki.laptop.org/go/Schoolsplay
http://gvr.sf.net and http://wiki.laptop.org/go/Guido_van_Robot

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Flávio Martins (flavioxmartins) wrote :

The bug is fixed upstream already.
In kernels with version number later than 2.6.22.
Setting Fix Released.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
nerling (nerling) wrote :

I'm having the same Problem in a Hardy installed on a acer travelmate 430.
uname -a:
Linux nerling-laptop 2.6.24-26-rt #1 SMP PREEMPT RT Tue Dec 1 20:53:25 UTC 2009 i686 GNU/Linux

Changed in linux:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.