From: bernard@blackham.com.au
To: Pavel Machek <pavel@ucw.cz>
Cc: Shaw <shawv@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: Screwy clock after apm suspend
Date: Mon, 10 Jan 2005 15:44:22 +0800 [thread overview]
Message-ID: <20050110074422.GA17710@mussel> (raw)
In-Reply-To: <200501092328.54092.shawv@comcast.net>
On Sun, Jan 09, 2005 at 11:28:53PM -0800, Shaw wrote:
> On Sunday 09 January 2005 02:47 pm, Pavel Machek wrote:
> > Probably code to compensate clock after ACPI suspend breaks apm case
> >
> > arch/i386/kernel/time.c, can you comment out
> > jiffies += sleep_length * HZ;
> >
> > in timer_resume to see if it goes away?
>
> Worked like a charm. I'm not seeing any time drift after your suggested
> change.
AIUI, this also means that a machine's uptime does not include time
whilst suspended. This was the behaviour prior to 2.6.10 and seems to be
more desirable as it counts the time the machine is actually running,
not just time since boot. Is there a good reason why we can't go back to
this?
Bernard.
next prev parent reply other threads:[~2005-01-10 7:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 18:08 Screwy clock after apm suspend 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-01-15 18:30 Mikael Pettersson
2005-01-16 19:47 ` Alex Romosan
2004-12-29 11:38 Mikael Pettersson
2005-01-03 17:34 ` Pavel Machek
2004-12-29 0:29 Brannon Klopfer
2004-12-29 1:18 ` Nigel Cunningham
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=20050110074422.GA17710@mussel \
--to=bernard@blackham.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=shawv@comcast.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