From: Jon Valvatne <jon-hc6/xhmWZxdWk0Htik3J/w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.6.9 S4: clock not updated after resume
Date: Sat, 23 Oct 2004 15:03:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20041023T170041-953@post.gmane.org> (raw)
In-Reply-To: 4178C072.1020905@pca.it
Luca Capello <luca@...> writes:
>
> Hi Pavel,
>
> on 10/21/04 22:20, Pavel Machek wrote:
> > It is a bug, here's the fix.
> actually, your fix doesn't work, as you can see from the attached
> syslog: I still need to synchronise the clock via NTP.
>
Maybe I'm missing something here, but if the problem is that the
kernel doesn't update the system clock from the hardware clock on
resume, why bother with NTP? Can't you just do a hwclock --hctosys?
Of course, the proper way is for the kernel to do it, I'm just saying..
Jon
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-23 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 12:21 2.6.9 S4: clock not updated after resume Luca Capello
[not found] ` <4177A9DC.7060503-wlebWZzHoyE@public.gmane.org>
2004-10-21 20:20 ` Pavel Machek
[not found] ` <20041021202051.GA21624-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-22 8:10 ` Luca Capello
2004-10-23 15:03 ` Jon Valvatne [this message]
[not found] ` <loom.20041023T170041-953-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2004-10-23 17:49 ` Luca Capello
[not found] ` <417A99B4.40707-wlebWZzHoyE@public.gmane.org>
2004-10-26 20:01 ` Luca Capello
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=loom.20041023T170041-953@post.gmane.org \
--to=jon-hc6/xhmwzxdwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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