Re: Re: Re: clock messed up

Giuseppe Ghib=F2 wrote:
> Thomas Backlund ha scritto:
>> 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 ?
>

That was of course powernow-k8..

> No.
>
>>
>> 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?
>

It already exists atleast Community Contrib for 2006 x86_64

>>
>> 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=20
>> Cool&Quiet driver fixed similar problems on Windows XP x64 edition...
>>
>> 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.
>

Yep.
Thats why you need the powernowd demon to manage the powernow-k8 module..=
.

It works great here
...
Thomas