Screwy clock after apm suspend

[Brannon Klopfer <plazmcman@softhome.net>]

2.6.10
Slackware 10/-current
IBM ThinkPad 600E
----------------

2.6.10 screws up my system clock.
Two kernel/hardware clock readings, before and after suspend.
-------------
plaz@gonzo:~$ date ;hwclock
Tue Dec 28 15:52:39 PST 2004
Tue Dec 28 14:54:07 2004 -0.503621 seconds
#suspend, resume
plaz@gonzo:~$ date ;hwclock
Tue Dec 28 16:11:58 PST 2004
Tue Dec 28 15:04:06 2004 -0.168262 seconds
---------------------
These are all when the comp is on without suspend (difference about the 
same throughout).
----------------
plaz@gonzo:~$ date ;hwclock
Tue Dec 28 16:14:52 PST 2004
Tue Dec 28 15:07:00 2004 -0.251812 seconds
plaz@gonzo:~$ date ;hwclock
Tue Dec 28 16:15:26 PST 2004
Tue Dec 28 15:07:34 2004 -0.236138 seconds
plaz@gonzo:~$ date ;hwclock
Tue Dec 28 16:19:48 PST 2004
Tue Dec 28 15:11:57 2004 -0.908540 seconds
plaz@gonzo:~$
------------
I did not have this problem with 2.6.9. My machine uses APM, clock 
stores local time (specified in kernel config). I use PIT for 
timesource, as others were losing ticks when on battery power (changes 
CPU clock speed). Again, did _not_ have this problem with 2.6.9.

Be glad to try out patches,
Brannon Klopfer