Re: Re: Re: clock messed up

Thomas Backlund ha scritto:
> Giuseppe Ghib=F2 wrote:
>=20
>>
>> 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.1=
s,
>> while on a working machine it won't go beyond 0.001s. Which means
>> clock is 100-1000 times less precise.
>=20
>=20
> Are you using powernow-k7 & powernowd ?

No.

>=20
> If not, can you try it?

no, which version? Note that I'm not on cooker and
there isn't the powernow package. Which version should
be backported?

>=20
> If you are using them, can you try without them ?
>=20
> Does it make any difference?
>=20
> 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...
>=20
> The powernow-k8 is the closest thing we have to that...

On 2007.0 (but not the same motherboard) powernow has the
side effect of dropping the clock from 2.4 to 1.0Ghz on both cores.

Bye
Giuseppe.