On 2006-12-17 21:04, John Andersen wrote:
> On Sunday 17 December 2006 03:42, Mark Hounschell wrote:
>   
>> Mark Hounschell wrote:
>>     
>>
>> Remember the original problem IS NOT an NTP problem. The guys clock runs
>> to fast.
>>     
>
> No it doesn't run too fast.
>   
Well, yes, it does. The system clock is far more than just a hardware
counter. It also consists of a kernel module that takes a raw count from
some counter and translates that into real time.
> Byte specifically stated his clock was just find on prior releases
> and in other OSs.  Its only the latest version of Suse that
> is giving him fits.
>   
Which suggests a bug in the kernel clock module. See also jdd's reply to
my "what is clock=pit" query, specifically the URL mentioned.

-- 
The best way to accelerate a computer running Windows is at 9.81 m/s²

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to