Comment 16 for bug 558627

Revision history for this message
Peter Curtis (pdcurtis) wrote :

I can confirm I am also seeing the problem on an MSI Wind U100 (with original bios) and had found the fix using setting 'use_time_for_policy' to FALSE works. The problem occurs with two different batteries.

Looking at the various charts one can view using the gnome-power-manager gui there seems to be a lot of random large values after a unplugging and plugging in the adapter both in charge and discharge times.

Excerpt from upower --dump shortly after a change shows

.........
   state: discharging
    energy: 22.3998 Wh
    energy-empty: 0 Wh
    energy-full: 22.6218 Wh
    energy-full-design: 24.42 Wh
    energy-rate: 11.3775 W
    voltage: 12.152 V
    time to empty: 2.0 hours
    percentage: 99.0186%
    capacity: 92.0455%
  History (charge):
    1273505398 99.019 discharging
    1273505367 99.460 discharging
    1273505336 99.902 discharging
  History (rate):
    1273505398 11.377 discharging
    1273505367 11.466 discharging
    1273505336 11.400 discharging
    1273505334 13.120 discharging
    1273505332 727.438 discharging

Daemon:
  daemon-version: 0.9.1

............
There seem to be two 'extra' anomalous readings in the rate history which do not match readings in the charge history. The idea of a delay seems a good one until real cause is found especially if it is Bios related.

I hope this can be fixed soon as such problems give Linux a bad name especially with owners of MSI machines after all the problems with Karmic. It took me 4 hours to find a fix and another hour before I came to this bug report hidden amongst many others for the gnome-power-manager. It wold have taken a lot longer if I did not know about and use gconf-editor. I am keeping our other Wind on Jaunty a bit longer which has behaved flawlessly for a year.