Red Hat Bugzilla – Bug 490684
suspending laptop causes power manager to fail to recognize power status
Last modified: 2009-12-18 04:02:44 EST
Description of problem: i'm using kernel 22.214.171.124-170.2.24.fc10.x86_64 with fedora 10 on an hp pavilion laptop model dv7-1174ca. when i close the laptop lid to suspend the laptop and re-open it the power manager icon in the notification area shows a critically low battery level. this happens whether the laptop is plugged in to ac or running on a full battery. also, if it is running on a battery, after i re-open the lid the power profile for plugged in is the one that controls the computer ie. dimming backlight etc.
Version-Release number of selected component (if applicable): 2.24.4-1
Steps to Reproduce:
1. suspend laptop
2. wake up from suspend
3. check battery or power status
Actual results: power status is not recognized and battery power is listed as critical
Expected results: should recognize actual power status
which component should i assign this to?
I already reassigned it to gnome-power-manager, its up to hughsie if it gets reassigned elsewhere now. :)
(In reply to comment #3)
> I already reassigned it to gnome-power-manager, its up to hughsie if it gets
> reassigned elsewhere now. :)
thanks for the help, i'm fairly new to bug reporting
Same problem on an HP Pavilion dv4-1125br.
I believe it should be reassigned to kernel or whatever package handles ACPI.
Im my machine, before suspend I can get battery information in /proc/acpi/battery/BAT0/state . After the suspend/resume, BAT0/state shows not present. So, it seems g-p-m can do nothing about it.
This happens both in F10 and in rawhide. Current kernel: 126.96.36.199-52.fc11.x86_64
This bug is a duplicate of bug #492576
*** Bug 492576 has been marked as a duplicate of this bug. ***
Still happens with F11?
Yes, with kernel 188.8.131.52-217.2.8.fc11.x86_64.
Confirmed on an HP Pavillion-dv7t 1000 running Fedora 11 184.108.40.206-217.2.16.fc11.x86_64
Solved. See http://patchwork.kernel.org/patch/35062/
See also http://bugzilla.kernel.org/show_bug.cgi?id=13745
Thanks for the tip Gadi!
However, the patches you have linked do not solve this particular issue as the hardware is different.
I've created a patch to fix it for the dv4. I applied it to the current F11 kernel and it fixes the issue. I uploaded it to the upstream bug for my laptop: http://bugzilla.kernel.org/show_bug.cgi?id=13449
dv7 owners: post the output of "dmidecode | grep -i product" and I can produce a patch for your machines for you to test.
Also, can someone please reassign this to kernel? Maybe the Fedora maintainer will find this simple and important enough for a kernel update to F11/F12.
Reassigning to kernel.
Patches for this issue for dv4 and dv7 laptops are in the Linus tree for 2.6.32.
They can easily backported to 2.6.30 and 2.6.31 for Fedora 11 and 12.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This bug is still present in F11 and F12.
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.