On Fri, 2007-12-07 at 02:16 +0100, Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> The Thursday 2007-12-06 at 09:02 -0800, Robert Smits wrote:
> 
> >> It seems a kernel problem, not an NTP problem.
> >
> > Actually, it looks way more like a hardware problem than a software problem.
> > Normally I can run any of my systems for more than a month without being 
> > more
> > than a minute or two off. Have you considered that the backup battery may be
> > low, or that you have a power supply problem?
> 
> Please, remember that the system time does not use the cmos clock and 
> battery at all. That's a different clock altogether. Plus, the cmos clock 
> is running fine, I'm checking it at the moment.
> 
> 
> > Of course, one way to check it is if the same hardware shows different 
> > timing
> > problems is to reinstall 10.2 but I know what a PITA that is.
> 
> It is very simple:
> 
>    1 Nov 11:28:02 ntpd[4669]: time reset +0.493571 s
>    1 Nov 19:54:33 ntpd[6168]: time reset +0.324889 s
>    2 Nov 11:56:25 ntpd[6168]: time reset +0.493251 s
>    2 Nov 14:09:49 ntpd[6168]: time reset +0.761453 s
>    2 Nov 18:57:50 ntpd[6168]: time reset +0.267648 s
>    2 Nov 19:19:37 ntpd[6168]: time reset +0.633949 s
>    3 Nov 15:04:26 ntpd[4993]: time reset +13.963114 s   <=== upgrade to 10.3
>    3 Nov 16:14:24 ntpd[4993]: time reset +126.365828 s
>    3 Nov 19:12:32 ntpd[5051]: time reset +42.074367 s
>    4 Nov 12:46:09 ntpd[5076]: time reset +22.996088 s
>    4 Nov 13:32:56 ntpd[5076]: time reset +393.672856 s
>    5 Nov 13:35:23 ntpd[5163]: time reset +351.141250 s
> 
> 
> You see how the resets increase just the very day I upgraded to 10.3? It 
> is thus a demonstration that it is a software problem. I do have a 
> partition with 10.2, I could try that one again. But there is no need, the 
> above log proves it.
> 

Well proven,

Latest patches were applied?
My college builded last week a 10.3 system with truly very strange
behaviour. We found out that the system clock --> was standing stil <--.

Havoc! 
ntp would not work (drift to large), could not update,
Only after a manually ntpdate he could repair the system.

btw, you know that you have to be carefull with xen & time...
(don't know if this relevant in your case)

hw
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to