Re: Re: Re: clock messed up

Giuseppe Ghib=F2 wrote:
>
> Sound that the fix for clock is not enough. With
> 2.6.12-25.tmb1mdksmp, running:
>
> watch -n 1 "ntpdate -d <timesource> 2>&1|grep offset"
>
> will show that after a few minutes (3-4) the drift is already >=3D 0.1s=
,
> while on a working machine it won't go beyond 0.001s. Which means
> clock is 100-1000 times less precise.

Are you using powernow-k7 & powernowd ?

If not, can you try it?

If you are using them, can you try without them ?

Does it make any difference?

The reason I ask is that I read on VMVare forum that the AMD Cool&Quiet=20
driver fixed similar problems on Windows XP x64 edition...

The powernow-k8 is the closest thing we have to that...

BTW,
I have a MSI K8N Neo4-FI with an AthlonX2 3800+ that I'll be installing=20
2007 Beta1 on in Tomorrow or the day after, so I'll install a 2006.0 too=20
to have an own testsystem ;-)

--
Thomas