Hi,
I am sorry but I cannot find the origin of the problem. Since 2.5.70, my
kernel has a lot of problems with its clock.
Take a look :
while ; do ntpdate -u ntp.tuxfamily.net ; sleep 2 ; done
23 Jun 14:53:17 ntpdate[2018]: step time server 80.67.179.98 offset -1764.508569 sec
23 Jun 14:53:18 ntpdate[2020]: step time server 80.67.179.98 offset -1.098748 sec
23 Jun 14:53:19 ntpdate[2022]: step time server 80.67.179.98 offset -1.081569 sec
23 Jun 14:53:20 ntpdate[2024]: step time server 80.67.179.98 offset -1.115521 sec
23 Jun 14:53:22 ntpdate[2026]: step time server 80.67.179.98 offset -1.096497 sec
23 Jun 14:53:23 ntpdate[2028]: step time server 80.67.179.98 offset -1.097201 sec
23 Jun 14:53:24 ntpdate[2031]: step time server 80.67.179.98 offset -1.081953 sec
23 Jun 14:53:26 ntpdate[2033]: step time server 80.67.179.98 offset -1.097588 sec
23 Jun 14:53:26 ntpdate[2035]: step time server 80.67.179.98 offset -1.577733 sec
23 Jun 14:53:28 ntpdate[2037]: step time server 80.67.179.98 offset -1.089877 sec
23 Jun 14:53:29 ntpdate[2039]: step time server 80.67.179.98 offset -1.116014 sec
23 Jun 14:53:30 ntpdate[2041]: step time server 80.67.179.98 offset -1.080928 sec
23 Jun 14:53:31 ntpdate[2043]: step time server 80.67.179.98 offset -1.098849 sec
I am running an AuthenticAMD mobile AMD Duron(tm) Processor with an ALi
Corporation M1647 Northbridge
If you give me some advices, i'll be able to provide more information
about this bug. For instance I don't see anything strange in the syslog.
Cheers,
--
Pierre Machard
<[email protected]> TuxFamily.org
<[email protected]> techmag.info
+33(0)668 178 365 http://migus.tuxfamily.org/gpg.txt
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87
On Mon, 2003-06-23 at 06:28, Pierre Machard wrote:
> I am sorry but I cannot find the origin of the problem. Since 2.5.70, my
> kernel has a lot of problems with its clock.
[snip]
> I am running an AuthenticAMD mobile AMD Duron(tm) Processor with an ALi
> Corporation M1647 Northbridge
Boot w/ "clock=pit" for now as a workaround.
If you're interested, check out bugme bug 827
http://bugme.osdl.org/show_bug.cgi?id=827 for more details and if you're
feeling adventurous you could help test the patch I'm working on to fix
this.
thanks
-john