2.6.8.1 slews system clock
Hi,
after updating kernel to 2.6.8.1 the system clock slews by 1 second every 10 seconds into future. I tried turning off ACPI, but that had no effect.
root@largo:~# ntpdate tik.cesnet.cz;sleep 10;ntpdate tik.cesnet.cz 20 Aug 13:55:01 ntpdate[5315]: step time server 195.113.144.201 offset -24.488611 sec 20 Aug 13:55:13 ntpdate[5321]: step time server 195.113.144.201 offset -1.042110 sec
on second machine the effect is opposite, ie the clock slews backwards. Any ideas?
Thanks,
--
Jan Spitalnik
[email protected]
Quoted 11 lines · Jan Spitalnik
after updating kernel to 2.6.8.1 the system clock slews by 1 second every 10 seconds into future. I tried turning off ACPI, but that had no effect.
root@largo:~# ntpdate tik.cesnet.cz;sleep 10;ntpdate tik.cesnet.cz 20 Aug 13:55:01 ntpdate[5315]: step time server 195.113.144.201 offset -24.488611 sec 20 Aug 13:55:13 ntpdate[5321]: step time server 195.113.144.201 offset -1.042110 secon second machine the effect is opposite, ie the clock slews backwards. Any ideas?
Which was the last kernel that worked?
Dne pá 20. srpna 2004 16:02 Tim Schmielau napsal(a):
Quoted 10 lines · Jan Spitalnik
Quoted 9 lines
after updating kernel to 2.6.8.1 the system clock slews by 1 second every 10 seconds into future. I tried turning off ACPI, but that had no effect.
root@largo:~# ntpdate tik.cesnet.cz;sleep 10;ntpdate tik.cesnet.cz 20 Aug 13:55:01 ntpdate[5315]: step time server 195.113.144.201 offset -24.488611 sec 20 Aug 13:55:13 ntpdate[5321]: step time server 195.113.144.201 offset -1.042110 sec
Quoted 4 lines
Quoted 2 lines
on second machine the effect is opposite, ie the clock slews backwards. Any ideas?
Which was the last kernel that worked?
2.6.7 didn't exhibit this problem. I will test 2.6.8-rc's to find which one caused this regression.
Signature · 2 lines
Jan Spitalnik [email protected]
Dne pá 20. srpna 2004 17:02 Jan Spitalnik napsal(a):
Quoted 4 lines
Quoted 1 line
Which was the last kernel that worked?
2.6.7 didn't exhibit this problem. I will test 2.6.8-rc's to find which one caused this regression.
Hi,
I've did further testing and I've found out that fortunately it's not a kernel problem (sorry for the buzz :-/ ). adjtimex was the culprit. adjtimexconfigure said that the CMOS clock is faster by 970secs a day to system clock. When I disabled adjtimex and rebooted, the system clock is now rock solid and doesn't slew. Now I wonder what's wrong with adjtimex or my system. I've tried on several other systems and the it was all the same. Thanks,
jan
Signature · 2 lines
Jan Spitalnik [email protected]