Clock Problem on AMD64 - Fedora Core 4

[Justin Conover]

On Apr 1, 2005 12:10 PM, Peter Jones <pjones at redhat.com> wrote:
> On Thu, 2005-03-31 at 21:37 -0500, Marc M wrote:
> > > if you are using NTP you should use a local NTP server (same time zone)
> > > I have had the same prob on my FC3 Notebook and I only could fix it with
> > > changing the NTP server I used.
> > > some how the NTP request is overwirting all the other settings.
> >
> >
> > --Ok, will do, thanks.  And yes I am EST.
> >
> > ---In answer to Bret's question, yes, when I run timeconfig, the
> > 'system clock uses UTC' is indeed checked.
> >
> > --Oh, and this is a dual boot with windblows that I haven't bothered
> > removing,  if windblows is the problem I will eradicate that.  How do
> > I know for sure that windblows is the problem here?
> 
> It is -- well, sortof.  If you boot into windows, it reads the hardware
> clock, which it doesn't know is UTC.  So it thinks that's the local
> time.  If the time is corrected (i.e. with something like ntp, or by
> manual update, or whatever), then it'll write the local time to the hw
> clock.
> 
> So then, when you reboot to Linux, it reads the local time from the hw
> clock, but it thinks it's reading UTC.  So it's off by your timezone
> offset.
> 
> The solution is to either not use UTC, not dual boot, or to make sure
> Windows never updates the time.  Ever.  At all.
> 
> --
>         Peter
> 
> --
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list
> 

I'm getting some clock problems on my fc3-x86_64 box too.  I can loose
time pretty fast and here is something from dmesg

warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip 0x2a95716bda