Apparently that is not enough, since I have g-p-m 2.16.1, yet it
sometimes decides to hibernate when my battery is over 80% full.  Last
time this happened on Jan 30 (after a fresh reinstall of Edgy), then I
changed the battery low action to "do nothing".  Here's my
/var/log/syslog:

  * last message before suspend:

Jan 30 19:29:45 pitonas NetworkManager: <WARNING>^I
nm_device_802_11_wireless_get_mode (): error getting card mode on eth1:
No such device

  * first message after resume:
  
Jan 30 21:56:40 pitonas kernel: [17353412.340000] Freezing cpus ...
...
Jan 30 21:56:40 pitonas gnome-power-manager: (mg) Kompiuteris budinamas

  (yay for localized syslog messages...NOT.  This means "computer is
waking up")

...
Jan 30 21:56:49 pitonas kernel: [17362230.156000] ACPI: Power Button (FF) [PWRF]
Jan 30 21:56:49 pitonas kernel: [17362230.156000] ACPI: Lid Switch [LID]
Jan 30 21:56:49 pitonas kernel: [17362230.156000] ACPI: Sleep Button (CM) [SLPB]
...
Jan 30 21:56:49 pitonas kernel: [17362230.272000] ACPI: Thermal Zone [THM0] (34 
C)
Jan 30 21:56:49 pitonas kernel: [17362230.308000] ibm_acpi: IBM ThinkPad ACPI 
Extras v0.12a
Jan 30 21:56:49 pitonas kernel: [17362230.308000] ibm_acpi: 
http://ibm-acpi.sf.net/
Jan 30 21:56:49 pitonas kernel: [17362230.384000] ACPI: AC Adapter [AC] 
(off-line)
Jan 30 21:56:49 pitonas kernel: [17362230.424000] ACPI: Battery Slot [BAT0] 
(battery present)
...
Jan 30 21:56:59 pitonas gnome-power-manager: (mg) Ekrano tęsimas nes neveiklumo 
režimas pasibaigė
  (no idea what this mean... "screen continuing because mode of inactivity is 
over", and it sounds that awkward in Lithuanian too)
Jan 30 21:56:59 pitonas gnome-power-manager: (mg) Vėl įjungiamas LCD skydelis 
nes neš. kompiuterio dangtis atvožtas
  (turning on LCD because the lid is open)
...
Jan 30 21:57:04 pitonas ntpdate[9586]: step time server 82.211.81.145 offset 
-4.170964 sec
...
Jan 30 21:57:09 pitonas gnome-power-manager: (mg) Hibernuojamas kompiuteris nes 
baterijos energijos lygis kritiškai mažas
   ("hibernating the computer because battery level is critical")

So, about three minutes after the kernel woke up.  The notification
baloon that mentioned the CRITICAL BATTERY LEVEL quoted these numbers:
84% full and 54 minutes.  (I wrote it down).

I woke it up immediatelly and could use it again from 21:59:39.

Here's my /var/log/acpid for that period of time:

[Tue Jan 30 19:29:38 2007] completed event "battery BAT0 00000080 00000001"
[Tue Jan 30 21:56:40 2007] received event "processor CPU 00000081 00000000"
[Tue Jan 30 21:56:40 2007] notifying client 6878[106:110]
[Tue Jan 30 21:56:40 2007] notifying client 5463[0:0]
[Tue Jan 30 21:56:40 2007] client has disconnected
[Tue Jan 30 21:56:40 2007] completed event "processor CPU 00000081 00000000"
[Tue Jan 30 21:56:49 2007] client connected from 5463[0:0]
[Tue Jan 30 21:56:49 2007] 1 client rule loaded
[Tue Jan 30 21:59:11 2007] client connected from 5463[0:0]
[Tue Jan 30 21:59:11 2007] 1 client rule loaded
[Tue Jan 30 22:04:56 2007] received event "battery BAT0 00000080 00000001"

I do not see anything else interesting in the log files.

-- 
Critical power warning at 99%
https://launchpad.net/bugs/42705

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to