Re: probable hardware bug: clock timer configuration lost

lonely wolf (wolfy@nobugconsulting.ro)
Fri, 21 Sep 2001 12:49:53 +0300


Benjamin LaHaise 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?

actually I get the message with RH's 7.1 stock kernel, with 2.4.7 (patched
with mosix 1.1.2) and with 2.4.9-ac12. it's always there, waiting for me. I
kind of think to remove the printk, just as Alan suggested, because they are
_very_ annoying. I have big hard disks, but I wouldn't like to have them
filled with logs containing mostly this message :)

--
      Manuel Wolfshant       linux registered user #131416
       network administrator    NoBug Consulting Romania
The degree of technical confidence is inversely proportional to the
level of management.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/