[lkml]   [2001]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: probable hardware bug: clock timer configuration lost
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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.033 / U:0.712 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site