[lkml]   [2004]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: get_cmos_time() takes up to a second on boot

On Fri, 7 May 2004, Tim Bird wrote:
> What is the downside of disabling this
> synchronization with the clock edge?

It might not matter any more, but if I remember correctly, the real
problem was that we used to always write back the time to the CMOS clock
too, and then booting a few times and consistently getting the time wrong
the same way made the clock drift quite noticeably.

These days, I think we do the write-back only if we use an external clock
(NTP), so we probably _could_ just remove the synchronization at
read-time (removing it at write-time doesn't sound like a good idea).

Does anybody remember better?

> 1 second of variability is unnacceptable
> when you're requirement is to boot in
> .5 seconds. :)

Heh. And yes, it could be handled other ways (you could check the cmos
time in the timer interrupt during boot, and correct it there rather than

> Would it be bad to disable this synchronization
> completely? How about just during boot?

I don't think we should necessarily disable the synchronization, but we
could certainly make it optional for cases that don't care about it. We
might even make the default be "don't care about the read

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-11-18 23:46    [from the cache]
©2003-2011 Jasper Spaans