Re: Low battery -> power down + clock set back to 1904-01-01
On Thu, 2004-01-22 at 22:38, Vincent Lefevre wrote:
> The battery of my PowerBook G4 got too low and the machine was put into
> sleep. I closed the lid, changed the battery, but when I reopened the
> lid, I noticed that the PowerBook was in fact off. And when I switched
> it on (around 21:00), the clock was set back to 1904-01-01. Here's a
> /var/log/syslog excerpt:
>
> Jan 22 20:45:36 ay kernel: eth0: switching to forced 10bt
> Jan 22 20:45:57 ay kernel: eth0: switching to forced 100bt
> Jan 22 20:46:04 ay kernel: eth0: switching to forced 10bt
> Jan 22 20:46:24 ay kernel: eth0: switching to forced 100bt
> Jan 22 20:46:29 ay pmud[762]: running /etc/power/pwrctl warning battery
> Jan 22 20:46:32 ay kernel: eth0: switching to forced 10bt
> Jan 22 20:46:39 ay pmud[762]: battery critically low: request system sleep
> Jan 22 20:46:39 ay pmud[762]: running /etc/power/pwrctl sleep battery
> Jan 22 20:46:40 ay pmud[762]: going to sleep
> Jan 1 00:15:17 ay syslogd 1.4.1#10: restart (remote reception).
> Jan 1 00:15:17 ay kernel: klogd 1.4.1#10, log source = /proc/kmsg started.
> Jan 1 00:15:17 ay kernel: Inspecting /boot/System.map-2.4.22-powerpc
> Jan 1 00:15:18 ay kernel: Loaded 22275 symbols from /boot/System.map-2.4.22-powerpc.
> Jan 1 00:15:18 ay kernel: Symbols match kernel version 2.4.22.
> Jan 1 00:15:18 ay kernel: Loaded 104 symbols from 4 modules.
> Jan 1 00:15:18 ay kernel: Memory BAT mapping: BAT2=256Mb, BAT3=0Mb, residual: 0Mb
> Jan 1 00:15:18 ay kernel: Total memory = 256MB; using 512kB for hash table (at c0380000)
> Jan 1 00:15:18 ay kernel: Linux version 2.4.22-powerpc (root@pegasos2) (gcc version 3.3.3 20040110 (prerelease) (Debian)) #1 Wed Jan 14 17:02:37 CET 2004
>
> Where does the problem come from? I've never had one like that before.
> As the kernel is quite new, I suspect that it is the cause.
I remember I had the same problem here. However I don't remember whether
erasing pmud (and replacing it with the much better pbbuttonsd) or
switching to kernel 2.6. fixed this issue for me.
Soeren
Reply to: