From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Sep 2001 22:16:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Sep 2001 22:15:53 -0400 Received: from host154.207-175-42.redhat.com ([207.175.42.154]:38795 "EHLO lacrosse.corp.redhat.com") by vger.kernel.org with ESMTP id ; Thu, 20 Sep 2001 22:15:46 -0400 Date: Thu, 20 Sep 2001 22:16:10 -0400 From: Benjamin LaHaise To: Alan Cox Cc: lonely wolf , linux-kernel@vger.kernel.org Subject: Re: probable hardware bug: clock timer configuration lost Message-ID: <20010920221610.A14451@redhat.com> In-Reply-To: <3BAA9008.9837EA52@nobugconsulting.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from alan@lxorguk.ukuu.org.uk on Fri, Sep 21, 2001 at 02:04:39AM +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 21, 2001 at 02:04:39AM +0100, Alan Cox wrote: > Its harmless. When we detect this we restore the state of the chip > correctly. If anything I should kill the printk but I'd still like to > figure the precise errata issue out Odd, I just got this during booting of my ALi based boards (never had seen it before). Are we certain the test is correct? -ben