Kernel Bug Tracker – Bug 9627
Regression: Battery method parse error
Last modified: 2008-10-29 15:36:41 UTC
Most recent kernel where this bug did not occur: 2.6.24-rc2
Distribution: Debian unstable
Hardware Environment: ULI Laptop
I noticed that my battery meter stopped working somewhere in the 2.6.24-rc series, so I did a bisect and found this:
Author: Alexey Starikovskiy <firstname.lastname@example.org>
Date: Thu Nov 15 21:52:47 2007 +0300
ACPI: EC: Don't init EC early if it has no _INI
Option to init EC early inserted to handle #8598 ASUS problem,
introduced several others.
EC driver in this particular case has fake _INI method, not present on
other machines, which don't need or break from this workaround, so lets use
its presence as a flag for early init.
Signed-off-by: Alexey Starikovskiy <email@example.com>
Signed-off-by: Len Brown <firstname.lastname@example.org>
Reverting this patch does indeed fix the problem with 2.6.24-rc6. I'll attach dmesg with and without patch, along with an acpidump.
Created attachment 14158 [details]
dmesg output with battery brokenness
Created attachment 14159 [details]
dmesg output fixed by reverting patch
Created attachment 14160 [details]
On Sun, 23 Dec 2007 13:00:19 -0800 (PST) email@example.com wrote:
Looks like another regression to track, please.
Created attachment 14170 [details]
Enable EC region handlers before bus_scan
Please check if this patch helps.
Sorry, no. I get the same error, with subtly different addresses.
bruce@moon:~/build/linux$ cut -f6- -d' ' /home/bruce/dmesg.bat| diff - /var/log/dmesg
> APIC error on CPU0: 40(40)
< APIC timer calibration result 12500398
> APIC timer calibration result 12500441
< ACPI Error (evregion-0316): No handler for Region [RAM_] (ffff810037804a40) [EmbeddedControl] 
> ACPI Error (evregion-0316): No handler for Region [RAM_] (ffff81003781aa40) [EmbeddedControl] 
< ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT0._STA] (Node ffff810037805180), AE_NOT_EXIST
> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT0._STA] (Node ffff810037819180), AE_NOT_EXIST
Could you please add some printk into acpi_boot_ec_enable() in ec.c?
Please check if it is executed _before_ your failing call to _STA.
Created attachment 14181 [details]
Enable EC region handlers before bus_scan #2
Please check this updated patch.
After applying this patch to 2.6.24-rc6-git1 the battery meter has started to work in my MSI-GX700 laptop.
Thank you very much!
But unfortunately it doesn't show the correct remaining time (the same as it was before 2.6.24-rc4):
design capacity: 1297 mAh
last full capacity: 12304 mAh
battery technology: rechargeable
design voltage: 38442 mV
design capacity warning: 0 mAh
design capacity low: 0 mAh
capacity granularity 1: 1 mAh
capacity granularity 2: 1 mAh
model number: MS-1719
battery type: LION
OEM info: MSI Corp.
capacity state: ok
charging state: charged
present rate: unknown
remaining capacity: unknown
present voltage: 10000 mV
Please open separate bug for this issue. Marking this bug as resolved.
Thanks for report and testing.
Wonderful. Yes I can also report that this patch resolves the bug. Thanks very much!
patch in comment #8 applied to acpi test branch
*** Bug 9697 has been marked as a duplicate of this bug. ***
I confirm that the patch does resolves the issue, and in my case the battery status show also correct discharge rate and remaining time.
*** Bug 9724 has been marked as a duplicate of this bug. ***
*** Bug 9663 has been marked as a duplicate of this bug. ***
patch in comment #8
shipped in linux-2.6.24-rc7-git5
*** Bug 9730 has been marked as a duplicate of this bug. ***
Created attachment 17497 [details]
try the debug patch to see whether the system will be affected by this patch
Hi, Mark && Bruce
Will you please try the debug patch and see whether the system will be affected by this patch?
Which kernel version would you like me to try this patch on?
Had better try the latest kernel. For example: 2.6.27-rc4(Of course 2.6.27-rc1/2/3 is also OK).
sorry I've missed the opportunity to test this patch.
However there is a new and possibly related bug, that I have submitted here: http://bugzilla.kernel.org/show_bug.cgi?id=11892
If you think your patch is still relevant I can try to apply it.
Thanks a lot.