From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S317298AbSHYLmw>; Sun, 25 Aug 2002 07:42:52 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S317312AbSHYLmw>; Sun, 25 Aug 2002 07:42:52 -0400
Received: from 203-79-122-66.cable.paradise.net.nz ([203.79.122.66]:8965 "EHLO
	ruru.local") by vger.kernel.org with ESMTP id <S317298AbSHYLmv>;
	Sun, 25 Aug 2002 07:42:51 -0400
Date: Sun, 25 Aug 2002 23:47:04 +1200
From: Volker Kuhlmann <list0570@paradise.net.nz>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel losing time
Message-ID: <20020825114704.GG11740@paradise.net.nz>
References: <20020825105500.GE11740@paradise.net.nz> <Pine.LNX.4.44.0208250459500.3234-100000@hawkeye.luckynet.adm>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0208250459500.3234-100000@hawkeye.luckynet.adm>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun 25 Aug 2002 23:01:19 NZST +1200, Thunder from the hill wrote:

> And it's already known. It's VIA chipset which obviously can't read the 
> clock ;-) Chipset kicking wrong interrupts, timer can't help it.

Ah, thanks! I did use google, but it's difficult to find the correct
words and numbers to enter...

Where can I find more information about it? Mainly, is this a problem
which can be solved at all, or do I need to get rid of the mobo
altogether?

Thanks,

Volker

-- 
Volker Kuhlmann			is possibly list0570 with the domain in header
http://volker.orcon.net.nz/		Please do not CC list postings to me.