Description of problem:
When the battery goes critical and gnome-power-manager hibernates the machine,
it gets stuck in a loop. If I plug in the AC and power up the machine, it
resumes, then immediately hibernates again. Near as I can tell, it will continue
to do this until the battery is 100% charged.
Manually triggered hibernation works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Unplug the AC
2. Let battery drain until critical
3. Plug in AC
4. Power machine back on
Machine resumes and then immediately hibernates again.
Machine should simply resume.
This is on a Compal N38N2 laptop, which near as I can tell is fairly obscure.
This particular model does not seem to have been OEM'ed to any big names, though
many other Compal models are. It has a mobile PIII 700E CPU, and a VIA chipset:
00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
00:04.0 CardBus bridge: Texas Instruments PCI1420
00:04.1 CardBus bridge: Texas Instruments PCI1420
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
30)00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97
Audio Controller (rev 20)
00:10.0 Communication controller: Conexant HSF 56k Data/Fax/Voice Modem (rev
01)01:00.0 VGA compatible controller: Trident Microsystems CyberBlade i1 (rev 6a)
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC
Created attachment 126013 [details]
lshal -m log
Created attachment 126014 [details]
can you "do: lshal -m" and then hibernate, resume and then attach the log
please. Many thanks.
I think I've fixed this.
Can you try gnome cvs please:
2006-03-13 Richard Hughes <email@example.com>
* data/gnome-power-manager.schemas.in, src/gpm-prefs.h: Add
/apps/gnome-power-manager/policy_suppression_timeout so we can start to ignore
events after we have returned from suspend/hibernate.
* src/gpm-manager.c (gpm_manager_is_policy_timout_valid): Add functionality so
we can ignore events from resume. This is adapted from the ubuntu mega-patch by
Daniel Silverstone. This should fix rh:185273.
Can someone package 2.14.0 for FC5 please -- it should fix this bug.
Sure, let me add it to the FC5 Update tracker, and we can push an update soon
after FC5. We already have a final tree candidate for the initial release of
FC5, so its too late for that.
Can you try the gnome-power-manager in updates-testing and report whether or not
it fixes your issues?
Seems to have fixed it. Thanks.
Great, pushed to updates