ntp messed up; where I start?

[sean]

sean wrote:
> ntp-4.2.2p4-2.fc7.x86_64
> 
> I set time and date this morning. Now at 16;45 local time, I show 23:09 
> on the computer. I've been seeing these huge fast times for about a week.
> 
> I've erased ntp  ( including all the /etc/ntp and /var/lib/ntp files ) 
> and reinstalled.
> 
> syslog shows that a restart makes it work ( notice the time jump ):
> 
> Jan  8 23:14:41 localhost ntpd[2913]: ntpd exiting on signal 15
> Jan  8 16:49:25 localhost ntpdate[10916]: step time server 62.206.253.10 
> offset -23128.011850 sec
> Jan  8 16:49:25 localhost ntpd[10918]: ntpd 4.2.2p4 at 1.1585 Wed Nov 22 
> 14:49:33 UTC 2006 (1)
> Jan  8 16:49:25 localhost ntpd[10919]: precision = 2.000 usec
> Jan  8 16:49:25 localhost ntpd[10919]: Listening on interface wildcard, 
> 0.0.0.0#123 Disabled
> Jan  8 16:49:25 localhost ntpd[10919]: Listening on interface wildcard, 
> ::#123 Disabled
> Jan  8 16:49:25 localhost ntpd[10919]: Listening on interface lo, 
> ::1#123 Enabled
> Jan  8 16:49:25 localhost ntpd[10919]: Listening on interface eth0, 
> fe80::215:f2ff:fe77:8613#123 Enabled
> Jan  8 16:49:25 localhost ntpd[10919]: Listening on interface lo, 
> 127.0.0.1#123 Enabled
> Jan  8 16:49:25 localhost ntpd[10919]: Listening on interface eth0, 
> 10.10.8.1#123 Enabled
> Jan  8 16:49:25 localhost ntpd[10919]: kernel time sync status 0040
> Jan  8 16:49:25 localhost ntpd[10919]: frequency initialized 0.000 PPM 
> from /var/lib/ntp/drift
> 
> ntpstat always shows:
> 
> ntpstat
> unsynchronised
>   time server re-starting
>    polling server every 64 s
> 
> ntpq shows me reaching the time servers ( notice how much offset already):
> 
> ntpq> pe
>      remote           refid      st t when poll reach delay   offset  
> jitter
> ============================================================================== 
> 
>  58.73.137.250   .GPS.            1 u   55   64  177 439.874  -102854 
> 69862.7
>  trogdor.ruka.or 64.142.103.194   2 u   61   64  177 192.566  -5814.1 
> 124198.
>  dnsserver.org   76.169.239.34    2 u   61   64  177 208.446  -6295.5 
> 124753.
> 
> 
> It's a three-month old mobo. It's dual boot, no problem in windows.
> 
> I don't know a lot about ntp, not enough to file a cogent bug report.
> 
> What should I be looking for?
> 
> sean
> 

Still messing around. Actual time is 5:30:

# date
Mon Jan  8 17:48:23 EST 2007
# hwclock
Mon 08 Jan 2007 05:30:41 PM EST  -1.028559 seconds


!!!

Any clues?

sean