All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: David Balazic <david.balazic@uni-mb.si>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Wrong clock initialization
Date: Tue, 20 May 2003 13:21:55 -0700	[thread overview]
Message-ID: <3ECA8E63.6080002@mvista.com> (raw)
In-Reply-To: <3ECA73AB.FBC470DB@uni-mb.si>

David Balazic wrote:
> george anzinger wrote:
> 
>>David Balazic wrote:
>>
>>>Hi!
>>>
>>>When the kernel is booted ( ia32 version at least ) , it reads
>>>the time from from the hardware CMOS clock , _assumes_ it is in
>>>UTC and set the system time to it.
>>>
>>>As almost nobody runs their clock in UTC, this means that the system
>>>is running on wrong time until some userspace tool corrects it.
>>>
>>>This can lead to situtation when time goes backwards :
>>>
>>>timezone is 2hours east of UTC.
>>>UTC time : 20:00
>>>local time : 22:00
>>>
>>>System time between boot and userspace fix : 22:00UTC
>>>System time after fix : 20:00UTC
>>>
>>>Comments ?
>>
>>During shut down my system "says" it is setting the CMOS clock from
>>the kernel clock.  I would expect this to correct the problem.  Is
>>this a distro thing?
> 
> 
> The time is properly converted first to be localtime, if your CMOS
> is localtime. So this does not fix anything.

Ouch!  That is a real disconnect.  Time to fix something.
> 
> 
>>In any case, this would seem to make the problem go away after the
>>first shutdown (if you don't dual boot with something other than Linux :).
> 
> 
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  reply	other threads:[~2003-05-20 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 17:34 Wrong clock initialization David Balazic
2003-05-20 18:08 ` David D. Hagood
2003-05-20 18:10 ` george anzinger
2003-05-20 18:27   ` David Balazic
2003-05-20 20:21     ` george anzinger [this message]
2003-05-20 18:17 ` Michael Buesch
2003-05-20 18:26   ` David Balazic
2003-05-20 20:16 ` Jan Harkes
2003-05-21 11:38 ` Jesse Pollard
2003-05-21 17:00 ` Jerry Cooperstein

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=3ECA8E63.6080002@mvista.com \
    --to=george@mvista.com \
    --cc=david.balazic@uni-mb.si \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.