[Pm-utils] No battery info after suspend

[Dan Nicholson]

On Thu, Feb 26, 2009 at 4:08 AM, Donald Harden <chedbh at langate.gsu.edu> wrote:
> Hello,
>
> I have the following:
>  HP Pavilion dv7 laptop with an Intel Core2 Duo T9400 and 4 GB of RAM
>   Fedora 10  2.6.27.15-170.2.24.fc10.x86_64
>   pm-utils-1.2.2.1-2.fc10
>   hal-0.5.12-14.20081027git.fc10
>
> Everything runs great including suspending, hibernating and resuming except that when the laptop resumes from a suspend or hibernation there is no battery info:
>  {0}duder:/home/don > cat /proc/acpi/battery/BAT0/alarm
>  present:                 no
>  {0}duder:/home/don > cat /proc/acpi/battery/BAT0/info
>  present:                 no
>  {0}duder:/home/don > cat /proc/acpi/battery/BAT0/state
>  present:                 no
>
> Before a suspend or hibernation  and resume the battery info is as expected:
>  {0}duder:/home/don/bin > cat /proc/acpi/battery/BAT0/info
>  present:                 yes
>  design capacity:         5100 mAh
>  last full capacity:      4800 mAh
>  battery technology:      rechargeable
>  design voltage:          14400 mV
>  design capacity warning: 240 mAh
>  design capacity low:     144 mAh
>  capacity granularity 1:  264 mAh
>  capacity granularity 2:  3780 mAh
>  model number:            Primary
>  serial number:
>  battery type:            Lion
>  OEM info:                Hewlett-Packard
>
>
> It does not matter if the laptop is running on AC power or the battery
>
> Booting with every combination of turning acpid on or off and turning the pci=noapci  kernel flag on or off  has no effect.
>
> I spent a good deal of time Googling and searching the pm-utils archives but found no solution.
>
> I've also tried the suggestions on the HAL Quirk site, http://people.freedesktop.org/~hughsient/quirk/index.html  but still no joy.
>
> Any ideas to get my battery info after a resume?

I just noticed this message. Don't know if you found an answer in the meantime.

This is almost certainly a kernel bug. pm-utils can work around some
things in userspace, but eventually it just tells the kernel to
suspend and hope it resumes in a usable state.

I would suggest trying a newer kernel version at least. Probably
advisable to open a Fedora bug. If that doesn't get you anywhere, you
can try the vanilla kernel.org kernels and contacting lkml.org,
linux-acpi at kernel.org and/or kernel.org bugzilla.

Also, you may want to look at dmesg to see if there's any messages
from the acpi subsystem.

--
Dan