-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-12-07 at 16:45 -0600, Rajko M. wrote:
Have you disabled: [*] Tickless System (Dynamic Ticks) this is new in 10.3 comparing to 10.2.
Not yet. I think I will compile the kernel tomorrow: it takes about three hours in this machine.
So, what happened Carlos. Any change?
Not yet, I couldn't... however, I have been running tests. I wrote a cronjob to compare the system clock to the cmos clock every 5 minutes, and the difference varies between 0 and 1 seconds for several hours. Then I disconnected the router, to force ntpd to be unable to connect to its peers... and not 1" error! No drift! I'm astonished. I have an email pending with some logs of this, I'll send it promptly. The only thing I did was to force the kernel to use the 'tsc' clock instead of the 'acpi_pm' clocksource it was using: Dec 7 01:59:21 nimrodel kernel: Time: tsc clocksource has been installed. I don't understand. The tsc source had given errors previously: Dec 6 22:14:08 nimrodel kernel: Clocksource tsc unstable (delta = 65620380907 ns) Dec 6 22:51:06 nimrodel kernel: set_rtc_mmss: can't update from 0 to 51 Dec 6 22:51:09 nimrodel syslog-ng[3946]: last message repeated 2 times Dec 6 22:51:09 nimrodel kernel: set_rtc_mmss: can't update from 1 to 51 Dec 6 22:51:35 nimrodel syslog-ng[3946]: last message repeated 22 times Dec 6 22:51:36 nimrodel kernel: set_rtc_mmss: can't update from 1 to 51 Dec 6 22:52:00 nimrodel syslog-ng[3946]: last message repeated 17 times I will have to watch this for a longer time, but... I wish I knew the difference of each type of clock, I could do an informed selection. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHWd+6tTMYHG2NR9URAu9nAJ437+abI7qgIBMdNCCruwbYEnlLtQCeIXit 2W5w2WJOJ5hnrpKSImA7CTc= =EpU8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org