From: Henry N. <hen...@ar...> - 2010-09-20 20:55:23
|
Hello Ron, On 20.09.2010 08:29, Ron Avriel wrote: > Hello Henry, > > Thanks a lot for debug version. I installed it, and I'm waiting for > the leap again. > > It's amazing that the exact same time offset was also seen by another > user. What's so special about this 30945 value? > Too bad it doesn't happen here every five seconds. It would have been > solved by now. If we would know. what it is, we would change it. But, currently it is a ghost on some computers only. ;-) > > Re the SF bug - our servers run latest Windows 2003, no virtual > machines. Our processor is Intel Pentium 4 1.4 GHz. > However cat /etc/adjtime > 0.000000 1162000000 0.000000 > 1162000000 > UTC > > I got the same output is from other machines as well. Is that > 1162000000 OK? Yes. The middle field says, when you have last set adjustment. It's the count of seconds since 1/1/1970: TZ= LANG= date --date="1970-01-01 +1162000000sec" Sat Oct 28 01:46:40 UTC 2006 > > BTW, from the output in the debug readme I saw that your server has > the same clock frequency as our leaping servers: freq=3579545. > I hope it will help solving this problem. > Have tested co_div64 against the div64_32 by simulate timediffs between 5 to 10*3579545, and have compaired the jiffies result and remainder for every timediff. Results are all exactly the same. See attched file. The output under Windows is the same as under Linux 32 bit: co_div64: 15 f co_div64: 983055 f000f div64_32: 16 10, rem:0 0 div64_32: 1048576 100000, rem:0 0 done -- Henry N. |