From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Brannon Klopfer <plazmcman@softhome.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: Screwy clock after apm suspend
Date: Wed, 29 Dec 2004 12:18:05 +1100 [thread overview]
Message-ID: <1104283084.16753.16.camel@desktop.cunninghams> (raw)
In-Reply-To: <41D1FA78.50203@softhome.net>
Hi.
We've seen this problem with Suspend2 as well. One of my Suspend2 users
has looked into the problem and suggested a couple of solutions; I'll
take a look at them shortly and send a patch here as well.
Regards,
Nigel
On Wed, 2004-12-29 at 11:29, Brannon Klopfer wrote:
> 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
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Nigel Cunningham
Cyclades Software Engineer
Canberra, Australia
http://www.cyclades.com
+61 (2) 6292 8028
+61 (417) 100 574
next prev parent reply other threads:[~2004-12-29 1:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 0:29 Screwy clock after apm suspend Brannon Klopfer
2004-12-29 1:18 ` Nigel Cunningham [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-29 11:38 Mikael Pettersson
2005-01-03 17:34 ` Pavel Machek
2005-01-07 18:08 Shaw
2005-01-09 22:47 ` Pavel Machek
2005-01-10 2:15 ` Alex Romosan
2005-01-10 7:28 ` Shaw
2005-01-10 7:44 ` bernard
2005-01-10 10:57 ` Pavel Machek
2005-01-10 17:48 ` Bernard Blackham
2005-01-11 0:14 ` Pavel Machek
2005-01-11 1:10 ` Nigel Cunningham
2005-01-11 3:12 ` Pavel Machek
2005-01-11 1:16 ` Bernard Blackham
2005-01-11 3:21 ` Pavel Machek
2005-01-11 12:36 ` Mikael Pettersson
2005-01-11 13:10 ` Pavel Machek
2005-01-11 14:15 ` Mikael Pettersson
2005-01-11 20:18 ` Pavel Machek
2005-01-11 3:13 ` Stephen Rothwell
2005-01-11 3:19 ` Pavel Machek
2005-01-11 12:32 ` Mikael Pettersson
2005-01-15 18:30 Mikael Pettersson
2005-01-16 19:47 ` Alex Romosan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1104283084.16753.16.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=plazmcman@softhome.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox