Bug 17832
Summary: | Cannot display status of two batteries in lenovo thinkpad | ||
---|---|---|---|
Product: | ACPI | Reporter: | Hanno Boeck (hanno) |
Component: | Power-Battery | Assignee: | Zhang Rui (rui.zhang) |
Status: | REJECTED DOCUMENTED | ||
Severity: | normal | CC: | acpi-bugzilla, rui.zhang, yakui.zhao |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.35.4 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
GBST method with debug info
GBST dmesg bat-status dmesg with bat1 discharging bat status with bat1 discharging dmesg with bat1 (/proc) discharging bat status with bat1 (/proc) discharging |
Description
Hanno Boeck
2010-09-05 15:32:34 UTC
Will you please attach the output of acpidump on your box? thanks. You can find acpidump and other data at http://int21.de/t61/data/ please attach the output of "grep . /proc/acpi/battery/*/*". /proc/acpi/battery/BAT0/alarm:alarm: 4233 mWh /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 84240 mWh /proc/acpi/battery/BAT0/info:last full capacity: 84670 mWh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 10800 mV /proc/acpi/battery/BAT0/info:design capacity warning: 4233 mWh /proc/acpi/battery/BAT0/info:design capacity low: 200 mWh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 1 mWh /proc/acpi/battery/BAT0/info:capacity granularity 2: 1 mWh /proc/acpi/battery/BAT0/info:model number: 42T4619 /proc/acpi/battery/BAT0/info:serial number: 7883 /proc/acpi/battery/BAT0/info:battery type: LION /proc/acpi/battery/BAT0/info:OEM info: SANYO /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: discharging /proc/acpi/battery/BAT0/state:present rate: 17887 mW /proc/acpi/battery/BAT0/state:remaining capacity: 52370 mWh /proc/acpi/battery/BAT0/state:present voltage: 11503 mV /proc/acpi/battery/BAT1/alarm:alarm: 1566 mWh /proc/acpi/battery/BAT1/info:present: yes /proc/acpi/battery/BAT1/info:design capacity: 31320 mWh /proc/acpi/battery/BAT1/info:last full capacity: 31320 mWh /proc/acpi/battery/BAT1/info:battery technology: rechargeable /proc/acpi/battery/BAT1/info:design voltage: 10800 mV /proc/acpi/battery/BAT1/info:design capacity warning: 1566 mWh /proc/acpi/battery/BAT1/info:design capacity low: 200 mWh /proc/acpi/battery/BAT1/info:cycle count: 0 /proc/acpi/battery/BAT1/info:capacity granularity 1: 1 mWh /proc/acpi/battery/BAT1/info:capacity granularity 2: 1 mWh /proc/acpi/battery/BAT1/info:model number: 51J0508 /proc/acpi/battery/BAT1/info:serial number: 1477 /proc/acpi/battery/BAT1/info:battery type: LiP /proc/acpi/battery/BAT1/info:OEM info: SONY /proc/acpi/battery/BAT1/state:present: yes /proc/acpi/battery/BAT1/state:capacity state: critical /proc/acpi/battery/BAT1/state:charging state: charged /proc/acpi/battery/BAT1/state:present rate: 0 mW /proc/acpi/battery/BAT1/state:remaining capacity: 0 mWh /proc/acpi/battery/BAT1/state:present voltage: 11081 mV Status is still needinfo, it seems I cannot change that myself, please re-open, I've provided all information you've asked for. Created attachment 31822 [details]
GBST method with debug info
custom GBST method.
please
1. download this GBST.aml file
2. mount debugfs by "mount -t debugfs none /sys/kernel/debug"
3. override the old method via the debugfs by running
"cat GBST.aml > /sys/kernel/debug/acpi/custom_method"
4. enable AML debug output by running
"echo 1 > /sys/module/acpi/parameters/aml_debug_output"
5. dmesg -c
6. grep . /proc/acpi/battery/*/* >bat-status
7. dmesg > dmesg
and then please attach the bat-status and dmesg file here.
Which kenrel options do I need to enable to be able to use the aml file? I have the sysfs-interface, but I get laverne Downloads # cat GBST.aml > /sys/kernel/debug/acpi/custom_method cat: write error: Invalid argument when I try to do that. so is /sys/kernel/debug/acpi/custom_method available? The interface file /sys/kernel/debug/acpi/custom_method exists but I can neither cat it nor cat something into it. Created attachment 32942 [details]
GBST
would you please try the new GBST.aml file attached? Created attachment 33132 [details]
dmesg
Created attachment 33142 [details]
bat-status
please redo the test and attach the dmesg/bat-status when BAT1 is discharging. Created attachment 33242 [details]
dmesg with bat1 discharging
Created attachment 33252 [details]
bat status with bat1 discharging
(In reply to comment #16) > Created an attachment (id=33252) [details] > bat status with bat1 discharging but this file shows that bat0 is still discharging, and bat1 is in critical status, i.e. the battery status doesn't change even if you switch the battery. do I miss something? What do you mean with switching the battery? I cannot switch them, they are two different kinds of batteries in different slots. (In reply to comment #17) > (In reply to comment #16) > > Created an attachment (id=33252) [details] [details] > > bat status with bat1 discharging > > but this file shows that bat0 is still discharging, and bat1 is in critical > status, i.e. the battery status doesn't change even if you switch the > battery. > do I miss something? Sorry, I mean the battery status, i.e. the output of "grep . /proc/acpi/battery/*/*" is the same when bat0 is discharging and when bat1 is discharging. Created attachment 33682 [details]
dmesg with bat1 (/proc) discharging
I think I found the reason for the confusion: the acpi command line tool shows the batteries in reverse order compared to the /proc-interface. So what I saw as bat1 was bat0 in proc.
Created attachment 33692 [details]
bat status with bat1 (/proc) discharging
well, the HB1S value read from EC is 0x00 when the bat0 is unknown and is 0x44 when it's discharging. This seems to be a firmware bug, and it should be described like this, bogus value got from firmware confuses the battery driver. IMO, you'd better check if this has been fixed in the new BIOS/EC firmware. I'm running latest BIOS available from lenovo. Is there anything I can do about it? It makes the second battery pretty useless. Any idea how I should report this to Lenovo? do you have a windows partition on this laptop? if yes, it would be great if you can verify if the problem exists in windows. |