Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000
Am Donnerstag, den 21.02.2013, 00:50 + schrieb Ben Hutchings: while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook- battery, upower still reports a charge capacity of 100% (AFAIK upower gets this information from the kernel - I believe this to be a kernel ACPI bug). The kernel driver doesn't do anything very interesting so it's actually very likely a BIOS bug. You were right, this really seems to be a BIOS bug. I checked the battery information in Windows with 'powercfg -energy': The reported values for 'Design capacity' (= ENERGY_FULL_DESIGN) and 'Last full charge' (= ENERGY_FULL) are the same: 59940. At first I thought that Windows gets the correct values because the charging level percentage reported by Windows corresponded to the percentage reported by the 'HP Support Assistant' program which shows me the correct battery info (including a realistic battery capacity value). I don't know why or how this works, but the charging level percentage seems to be quite accurate even if all the other reported values differ. I also used a freeware tool in Windows to get more information on the battery and it showed me the same info I get with 'cat /sys/class/power_supply/BAT1/uevent'. Apparently, for some systems and batteries, ACPI reports full capacity as 100 and current level as a percentage. In this case the ACPI battery driver cannot know what the true full capacity is. Its workaround is to assume it is equal to full design capacity. Unfortunately there doesn't seem to be any way to find out whether this workaround was enabled. The upstream maintainer, Lan Tianyu, provided a patch to comment the quirk (see comment #6 in the upstream report). However, after applying the patch the kernel reported the same values, so I guess the workaround wasn't enabled in my case. Since I can confirm that this is a BIOS bug I'm going to close this report. For more information please have a look at the upstream bug report. Thanks, Stefan. signature.asc Description: This is a digitally signed message part
Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000
I tested this also with debian kernel linux-image-3.7-trunk-amd64 (3.7.8-1~experimental.1) and with upstream kernel v3.7.9. Please tell me if I can provide more useful information. Stefan. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000
while my BIOS/UEFI reports a battery charge capacity of 92% for my
notebook-
battery, upower still reports a charge capacity of 100% (AFAIK
upower gets this
information from the kernel - I believe this to be a kernel ACPI
bug).
The kernel driver doesn't do anything very interesting so it's
actually
very likely a BIOS bug.
I checked the situation in Windows 7 over the last days and I don't see
the problem there. I can use the 'HP Support Assistant' in Windows to
check the battery capacity and status – it seems to be the same tool as
in the 'HP UEFI Support Environment'. The value 'Current' (in mAh)
accords to the values (in percentage of 'Full Charge Capacity') reported
by Windows.
This is why I don't think that this is a BIOS bug.
Can you send the contents of /sys/class/power_supply/BAT1/uevent so
we
at least know what the kernel is reporting?
stefan@rosa:~$ cat /sys/class/power_supply/BAT1/uevent
POWER_SUPPLY_NAME=BAT1
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Unknown
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1110
POWER_SUPPLY_VOLTAGE_NOW=10872000
POWER_SUPPLY_POWER_NOW=14851000
POWER_SUPPLY_ENERGY_FULL_DESIGN=5994
POWER_SUPPLY_ENERGY_FULL=5994
POWER_SUPPLY_ENERGY_NOW=17982000
POWER_SUPPLY_MODEL_NAME=Venturi
POWER_SUPPLY_MANUFACTURER=13-17
POWER_SUPPLY_SERIAL_NUMBER=01317 01/24/2012
Regarding my original issue ('GNOME fails to execute action on critical
battery condition') I just want to add that there seem to be three
issues involved: one is really a BIOS bug (see the last comments of
#695634), one at least seems to be a UPower bug (see #6841869) and then
there's this one.
Stefan.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000
Package: src:linux
Version: 3.2.35-2
Severity: normal
Dear Maintainer,
while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook-
battery, upower still reports a charge capacity of 100% (AFAIK upower gets this
information from the kernel - I believe this to be a kernel ACPI bug). I
suspect this issue to be part of my power problems reported in bug #695634 and
bug #684186 - my notebook fails to execute action (hibernate) on critical
battery condition. I'll add the information provided by UEFI (1.) and by upower
(2.).
(1.) Here's the information provided by the HP UEFI Support Environment:
Charge Capacity: 92%
Warranty Type: 1 year
Cycle Count: 187
Manufacturer: 13-17
Battery Age: 391 days
Serial Number: 01317 01/24/2012
Temperature: 36 °C
Design Capacity: 5400 mAh
Full Charge Capacity: 5020 mAh
Remaining Capacity: 2499 mAh
Current: 1797 mA
Battery Status: OK(1)
FAILURE ID: OK
Terminal Voltage: 11143 mV
Design Voltage: 11100 mV
Cell Voltage 1: 3710 mV
Cell Voltage 2: 3735 mV
Cell Voltage 3: 3700 mV
Cell Voltage 4: 0 mV
Status: 00C0
AC Power: No
CT Number: 6CLFH02BJ2E08M
(2.) Here's the information provided by upower ('upower --dump'):
Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path:
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0A:00/power_supply/BAT1
vendor: 13-17
model:Venturi
serial: 01317 01/24/2012
power supply: yes
updated: Wed Feb 20 23:57:03 2013 (23 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable:yes
state: discharging
energy: 28.771 Wh
energy-empty:0 Wh
energy-full: 59.94 Wh
energy-full-design: 59.94 Wh
energy-rate: 20.668 W
voltage: 11.103 V
time to empty: 1.4 hours
percentage: 47.9997%
capacity:100%
-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64
root=UUID=4f9dc00c-6e8b-431d-b71f-d7bbc5960ad8 ro quiet
** Tainted: C (1024)
* Module from drivers/staging has been loaded.
** Kernel log:
[3.432525] iwlwifi :02:00.0: pci_resource_len = 0x2000
[3.432529] iwlwifi :02:00.0: pci_resource_base = c90011088000
[3.432533] iwlwifi :02:00.0: HW Revision ID = 0x34
[3.432781] iwlwifi :02:00.0: irq 47 for MSI/MSI-X
[3.432898] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N
1030 BGN, REV=0xB0
[3.433028] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[3.448618] iwlwifi :02:00.0: device EEPROM VER=0x716, CALIB=0x6
[3.448620] iwlwifi :02:00.0: Device SKU: 0X150
[3.448623] iwlwifi :02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
[3.448652] iwlwifi :02:00.0: Tunable channels: 13 802.11bg, 0 802.11a
channels
[3.483191] mtrr: type mismatch for b000,1000 old: write-back new:
write-combining
[3.483196] [drm] MTRR allocation failed. Graphics performance may suffer.
[3.483773] i915 :00:02.0: irq 48 for MSI/MSI-X
[3.483780] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[3.483783] [drm] Driver supports precise vblank timestamp query.
[3.483824] vgaarb: device changed decodes:
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[3.490239] iwlwifi :02:00.0: firmware: agent loaded
iwlwifi-6000g2b-6.ucode into memory
[3.490248] iwlwifi :02:00.0: loaded firmware version 18.168.6.1
[3.490556] Registered led device: phy0-led
[3.496268] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[3.509769] input: HP TrueVision HD as
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input4
[3.509853] usbcore: registered new interface driver uvcvideo
[3.509856] USB Video Class driver (1.1.1)
[3.831764] input: HP WMI hotkeys as /devices/virtual/input/input5
[4.086773] rts_pstor: device scan complete
[4.087092] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S. 1.00
PQ: 0 ANSI: 0 CCS
[4.087242] Bad LUN (0:1)
[4.087546] Bad target number (1:0)
[4.087848] Bad target number (2:0)
[4.088152] Bad target number (3:0)
[4.088454] Bad target number (4:0)
[4.088758] Bad target number (5:0)
[4.089060] Bad target number (6:0)
[4.089314] Bad target number (7:0)
[4.089730] sd 6:0:0:0: Attached scsi generic sg1 type 0
[4.090411] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[4.116191] fbcon: inteldrmfb (fb0) is primary device
[4.308482] Console: switching to colour frame buffer device 170x48
[4.318392] fb0: inteldrmfb frame buffer device
[4.318397] drm: registered panic notifier
[4.325575] acpi device:33: registered as cooling_device6
[4.326327]
Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000
Control: tag -1 moreinfo
On Thu, 2013-02-21 at 00:24 +0100, Stefan Nagy wrote:
Package: src:linux
Version: 3.2.35-2
Severity: normal
Dear Maintainer,
while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook-
battery, upower still reports a charge capacity of 100% (AFAIK upower gets
this
information from the kernel - I believe this to be a kernel ACPI bug).
The kernel driver doesn't do anything very interesting so it's actually
very likely a BIOS bug.
I
suspect this issue to be part of my power problems reported in bug #695634 and
bug #684186 - my notebook fails to execute action (hibernate) on critical
battery condition. I'll add the information provided by UEFI (1.) and by
upower
(2.).
(1.) Here's the information provided by the HP UEFI Support Environment:
Charge Capacity: 92%
[...]
Design Capacity: 5400 mAh
Full Charge Capacity: 5020 mAh
[...]
Design Voltage: 11100 mV
OK, 5020/5400 ~= 0.92.
[...]
(2.) Here's the information provided by upower ('upower --dump'):
Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path:
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0A:00/power_supply/BAT1
vendor: 13-17
model:Venturi
serial: 01317 01/24/2012
power supply: yes
updated: Wed Feb 20 23:57:03 2013 (23 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable:yes
state: discharging
energy: 28.771 Wh
energy-empty:0 Wh
energy-full: 59.94 Wh
energy-full-design: 59.94 Wh
[...]
5400 mAh * 11100 mV = 59.94 Wh so energy-full-design looks good but
energy-full is wrong.
Apparently, for some systems and batteries, ACPI reports full capacity
as 100 and current level as a percentage. In this case the ACPI battery
driver cannot know what the true full capacity is. Its workaround is to
assume it is equal to full design capacity. Unfortunately there doesn't
seem to be any way to find out whether this workaround was enabled.
Can you send the contents of /sys/class/power_supply/BAT1/uevent so we
at least know what the kernel is reporting?
Ben.
--
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.
signature.asc
Description: This is a digitally signed message part
