Bug 543791 - F12 Regression: gnome-power-manager on VIA chipset: suspend on (dis)connect Power supply
Summary: F12 Regression: gnome-power-manager on VIA chipset: suspend on (dis)connect P...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-03 04:36 UTC by Andrew Jones
Modified: 2012-08-16 22:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 22:14:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andrew Jones 2009-12-03 04:36:07 UTC
Description of problem:
On connecting or disconnecting external power supply gnome-power-manager pops up an alert saying there remains 2 minutes battery life and suspends the computer.

Note that in my setup, gnome-power-manager is configured to HIBERNATE on critical battery condition

KDE Signals that power has been connected / disconnected but does nothing else

Version-Release number of selected component (if applicable):
gnome-power-manager 2.28.1-5.fc12


How reproducible:
   Fedora 11:  gnome-power-manager 2.26.4-3.fc11  No
   Fedora 12 - gnome-power-manager 2.28.1-5.fc12  100%

   Sample population of 3 notebooks booted from the same liveUSB 
     Intel Atom based notebook: No
     Intel Pentium M based notebook: No:
     Via C7-M based notebook: 100%  

     (The Via based PC also has F12 on hard disk - same results)

Steps to Reproduce:
1. Boot notebook on battery: login to Gnome
2. Connect external power

OR

1. Boot notebook with external power applied: login to Gnome
2. Disconnect external power
  
Actual results:
Popup states there remain 2 minutes of battery power
Notebook attempts to Suspend

(My hardware does not currently wake up from suspend under any circumstances so I cannot tell if suspend was successful)

Expected results:
Popup Notification that power has been connected or disconnected (with correct indication of battery longevity or time to charge as appropriate)
 

Additional info:
Here is the hardware of the Via based computer

00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX800 Host Bridge [1106:0353] (rev 12)
00:00.1 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Error Reporting [1106:1353]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Host Bus Control [1106:2353]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. VX800 PCI to PCI Bridge [1106:3353]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Power Management Control [1106:4353]
00:00.5 PIC [0800]: VIA Technologies, Inc. VX800/VX820 APIC and Central Traffic Control [1106:5353]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Scratch Registers [1106:6353]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 North-South Module Interface Control [1106:7353]
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. Device [1106:1122] (rev 11)
00:02.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:c353]
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:e353]
00:03.1 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:f353]
00:0c.0 SD Host controller [0805]: VIA Technologies, Inc. SDIO Host Controller [1106:95d0] (rev 10)
00:0d.0 FLASH memory [0501]: VIA Technologies, Inc. Secure Digital Memory Card Controller [1106:9530]
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VX800 Serial ATA and EIDE Controller [1106:5324]
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VX800/VX820 Bus Control and Power Management [1106:8353]
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 South-North Module Interface Control [1106:a353]
00:13.0 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:b353]
00:14.0 Audio device [0403]: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev 20)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8187SE Wireless LAN Controller [10ec:8199] (rev 22)

NON-Fedora-supplied drivers installed:
xf86-video-openchrome-0.2.904-build812   for the video adapter
Realtek Windows XP driver + rpmfusion NDISwrapper for the Wireless lan controller

Comment 1 Bug Zapper 2010-11-04 04:30:46 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Andrew Jones 2010-11-08 13:50:03 UTC
I confirm this is still happening on Fedora 13 and 14

After some experimentations it looks like gnome-power-manager is "doing the right thing", but doing it too quickly for my hardware.

I removed gnome-power-manager and installed acpitool and scripted acpitool to run continuously and record whenever anything changed.

Disconnected power at 12:51:00 and re-connected it at 12:51:30

2010-11-08T12:50:55	  Battery #1     : charging, 93.30%, 01:34:11
2010-11-08T12:51:00	  Battery #1     : discharging, 93.30%, 00:01:43
2010-11-08T12:51:04	  Battery #1     : discharging, 93.25%, 00:01:43
2010-11-08T12:51:09	  Battery #1     : discharging, 93.10%, 00:01:43
2010-11-08T12:51:13	  Battery #1     : discharging, 93.10%, 02:10:07
2010-11-08T12:51:14	  Battery #1     : discharging, 93.00%, 02:09:59
2010-11-08T12:51:18	  Battery #1     : discharging, 92.41%, 02:09:09
2010-11-08T12:51:23	  Battery #1     : discharging, 92.26%, 02:08:56
2010-11-08T12:51:27	  Battery #1     : discharging, 92.16%, 02:08:48
2010-11-08T12:51:30	  Battery #1     : charging, 92.16%, 00:00:08
2010-11-08T12:51:32	  Battery #1     : charging, 92.06%, 00:00:08
2010-11-08T12:51:35	  Battery #1     : charging, 92.06%, 00:00:09
2010-11-08T12:51:36	  Battery #1     : charging, 92.11%, 00:00:08
2010-11-08T12:51:51	  Battery #1     : charging, 92.16%, 00:00:08
2010-11-08T12:51:54	  Battery #1     : charging, 92.16%, 00:36:36
2010-11-08T12:52:09	  Battery #1     : charging, 92.21%, 00:36:22
2010-11-08T12:52:17	  Battery #1     : charging, 92.21%, 00:54:27
2010-11-08T12:52:39	  Battery #1     : charging, 92.26%, 00:54:06
2010-11-08T12:53:07	  Battery #1     : charging, 92.31%, 00:53:45
2010-11-08T12:53:15	  Battery #1     : charging, 92.31%, 01:48:08
2010-11-08T12:53:34	  Battery #1     : charging, 92.36%, 01:47:26
2010-11-08T12:53:37	  Battery #1     : charging, 92.36%, 00:53:24
2010-11-08T12:53:56	  Battery #1     : charging, 92.36%, 01:47:26
2010-11-08T12:54:10	  Battery #1     : charging, 92.41%, 01:46:44
2010-11-08T12:54:46	  Battery #1     : charging, 92.46%, 01:46:02

I see that for approximately 10 seconds after disconnecting power and 25 seconds after re-applying power the battery life calculation is wrong and indicates less than two minutes autonomy remaining.  So I understand why the computer hibernates / shuts down immediately.

This was a very cheap netbook with pre-installed Mandriva and I have no chance of getting any manufacturer support for Fedora.  Having looked at Smolt I suspect there is a maximum of one other PC of the same model in the Fedora community, so if this doesn't affect anyone else I don't really expect gnome-power-manager to be modified just for my case.

This is my PC
http://www.smolts.org/client/show/pub_3bd03d09-1ad5-4e8a-91b7-0d43fe841022

However if someone could give me a hint as to where I could modify gnome-power-manager to add some delay before shutting down I would be grateful.

Also if anyone could let me know if there is a way to check if it is my hardware or Fedora's acpi handling which is causing the battery life miscalculation I would again be grateful.

Otherwise close this bug 

Thanks,

Andrew Jones

Comment 3 Richard Hughes 2011-11-15 13:01:58 UTC
Does this still happen in F16? Thanks.

Comment 4 Fedora End Of Life 2012-08-16 22:14:22 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.