painfully slow recharge time when booted off battery

[Ben Howard]

Recharge times under Oneiric for my thinkpad w520 is _painfully_ slow. Estimates for recharging from around 50% is pegged at 12.5 to 13hrs. Under Natty, I was seeing recharge times around 1 to 2 hours for a 50% charge.

$ date && cat /proc/acpi/battery/BAT0/state
Fri Sep 9 12:01:42 MDT 2011
present: yes
capacity state: ok
charging state: charging
present rate: 224 mA
remaining capacity: 6446 mAh
present voltage: 11963 mV

$ date && cat /proc/acpi/battery/BAT0/state
Fri Sep 9 12:04:14 MDT 2011
present: yes
capacity state: ok
charging state: charging
present rate: 238 mA
remaining capacity: 6458 mAh
present voltage: 11984 mV

$ date && cat /proc/acpi/battery/BAT0/state [[ at this point, under Natty it would be recharged ]]
Fri Sep 9 14:41:32 MDT 2011
present: yes
capacity state: ok
charging state: charging
present rate: 330 mA
remaining capacity: 8483 mAh
present voltage: 12701 mV

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-10-generic 3.0.0-10.16
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ben 3943 F.... pulseaudio
 /dev/snd/controlC0: ben 3943 F.... pulseaudio
 /dev/snd/pcmC0D0p: ben 27237 F.... npviewer.bin
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xd4320000 irq 52'
   Mixer name : 'Conexant CX20590'
   Components : 'HDA:14f1506e,17aa21cf,00100000'
   Controls : 8
   Simple ctrls : 5
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xd3000000 irq 17'
   Mixer name : 'Nvidia GPU 14 HDMI/DP'
   Components : 'HDA:10de0014,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown'
   Mixer name : 'ThinkPad EC (unknown)'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Sep 9 12:00:16 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a6dc39d6-484d-428a-a527-65dde4acca7c
MachineType: LENOVO 4270CTO
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=d7a38d7a-5ea8-4ea7-8e61-c2f922171fe1 ro max_loop=254 nomodeset insmod=nivida
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-10-generic N/A
 linux-backports-modules-3.0.0-10-generic N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8BET44WW (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4270CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8BET44WW(1.24):bd05/13/2011:svnLENOVO:pn4270CTO:pvrThinkPadW520:rvnLENOVO:rn4270CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4270CTO
dmi.product.version: ThinkPad W520
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel currently in the release pocket than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help.

[Ben Howard (darkmuggle-deactivatedaccount)]

Confirmed with the latest kernel.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Scott Moser (smoser)]

smoser@brickies:~$ uname -r
3.0.0-12-generic
$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-3.0.0-12-generic: /boot/vmlinuz-3.0.0-12-generic
$ dpkg-query --show linux-image-3.0.0-12-generic
linux-image-3.0.0-12-generic 3.0.0-12.19

My system has been showing ~ 30 minutes to fully recharged for about an hour.

[Ben Howard (darkmuggle-deactivatedaccount)]

ben@padfoot:~$ uname -a
Linux padfoot 3.0.0-12-generic #19-Ubuntu SMP Fri Sep 23 21:23:39 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

For me, I may charge rate was substainly better and about what I would expect. I drained the battery to ~20% and then charged it back my default setting of 98% in 2 hours 13 minutes, which is about what I would expect.

Tue Oct 4 17:05:09 MDT 2011
charging state: charging
present rate: 3423 mA
remaining capacity: 2352 mAh
present voltage: 11548 mV

Tue Oct 4 19:18:29 MDT 2011
charging state: charged
present rate: 0 mA
remaining capacity: 9126 mAh
present voltage: 12912 mV

During the charge I took samples at 8.5 minute samples and saw:
present rate: 3423 mA
present rate: 3424 mA
present rate: 3426 mA
present rate: 3426 mA
present rate: 3423 mA
present rate: 3423 mA
present rate: 3423 mA
present rate: 3424 mA
present rate: 3427 mA
present rate: 3422 mA
present rate: 3047 mA
present rate: 2197 mA
present rate: 1569 mA
present rate: 1118 mA
present rate: 801 mA
present rate: 582 mA

---

Scott, on your next charge can you run:
while [ $( awk '/charging state/ {print$3}' /proc/acpi/battery/BAT0/state ) = "charging" ];
do
       date
       cat /proc/acpi/battery/BAT0/state
done | tee battery.log

When I was having the problem, I was seeing charge rates as low as 10 or 15mA.

[Ben Howard (darkmuggle-deactivatedaccount)]

I changed the title to reflect my latest finding. This bug is only observed when the laptop is booted on battery power.

To replicate:
1.) Boot thinkpad off battery
2.) Use for a bit
3.) Charge.

Thu Oct 6 16:23:37 MDT 2011
present: yes
capacity state: ok
charging state: charging
present rate: 437 mA
remaining capacity: 4325 mAh
present voltage: 11424 mV

Thu Oct 6 16:28:37 MDT 2011
present: yes
capacity state: ok
charging state: charging
present rate: 482 mA
remaining capacity: 4361 mAh
present voltage: 11450 mV

Taking the battery down to ~30 capacity at the present rate it will take ~11hours to charge. When booted off A/C, it would take ~2 hours to charge.

[Ben Howard (darkmuggle-deactivatedaccount)]

ben@padfoot:~/Desktop$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC
  native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:09/PNP0C09:00/ACPI0003:00/power_supply/AC
  power supply: yes
  updated: Thu Oct 6 16:25:46 2011 (939 seconds ago)
  has history: no
  has statistics: no
  line-power
    online: yes

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:09/PNP0C09:00/PNP0C0A:00/power_supply/BAT0
  vendor: LGC
  model: 42T4912
  serial: 20417
  power supply: yes
  updated: Thu Oct 6 16:41:21 2011 (4 seconds ago)
  has history: yes
  has statistics: yes
  battery
    present: yes
    rechargeable: yes
    state: charging
    energy: 49.6836 Wh
    energy-empty: 0 Wh
    energy-full: 103.885 Wh
    energy-full-design: 103.896 Wh
    energy-rate: 5.106 W
    voltage: 11.485 V
    time to full: 10.6 hours
    percentage: 47.8256%
    capacity: 99.9893%
    technology: lithium-ion
  History (charge):
    1317940881 47.826 charging
    1317940851 47.794 charging
    1317940821 47.729 charging
    1317940791 47.697 charging
  History (rate):
    1317940881 5.106 charging
    1317940851 5.261 charging
    1317940821 4.928 charging
    1317940791 5.017 charging

[Ben Howard (darkmuggle-deactivatedaccount)]

Snipped from "upower -d" after halt and power-on:

  battery
    present: yes
    rechargeable: yes
    state: charging
    energy: 70.0632 Wh
    energy-empty: 0 Wh
    energy-full: 103.885 Wh
    energy-full-design: 103.896 Wh
    energy-rate: 38.0175 W
    voltage: 12.269 V
    time to full: 53.4 minutes
    percentage: 67.4431%
    capacity: 99.9893%
    technology: lithium-ion

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Ben Howard (darkmuggle-deactivatedaccount)]

Issues remains. Marking as confirmed....again.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Ben Howard (darkmuggle-deactivatedaccount)]

I am unable to test the upstream kernel due to a kernel panic...the panic was too quick to find out the reason.

Removing tag.

[Joseph Salisbury (jsalisbury)]

@Ben

Would it be possible for you to try some of the earlier release candidates(rc8, rc7, rc6, etc) and see if they boot?

[Scott Moser (smoser)]

I'm virtually certain at this point that this bug is really with the unity panel battery applet.
I plugged in, and watched my battery charge go up at a reasonable rate by looking at
/sys/devices/platform/smapi/BAT0
and
/proc/acpi/battery/BAT0/

However, the applet showed me go from 21 minutes to full charge to 20, then to 22...
The actual percentage per 'remaining_percent' go from 78 to 89 over the course of 15 minutes.

[penalvch (penalvch)]

Declined for Oneiric as EOL -> Won't Fix

[penalvch (penalvch)]

Ben Howard, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]