On Fri, 9 Jan 2004 lkml _at_ nitwit.de wrote: > On Friday 09 January 2004 18:35, Jesper Juhl wrote: > > It's nothing to do with the OS most likely. Some BIOS's modify the FSB > > speed and other settings as a way to provide a sort of "fail safe" boot > > mode if a problem was detected. > > So, in your opinion I really have hardware problems (which yet didn't notice > and also for 3,5h did not recurr)? > All I'm saying is that I know for a fact that some BIOS's will do this (set bus speed to 100) if they detect problems - I know mine does. It's just one possibility. I don't actually /know/ what causes what you experienced. I guess it's possible that something the kernel did caused the BIOS to think there was a problem even though there was not... Or it could be something else entirely. I don't know for sure. All I can do is suggest that maybe you should check your motherboard manual for any hints on this behaviour and maybe try and test your hardware just to be safe... Other people probably have better advice for you. -- Jesper Juhl - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0.lkml
- Re: 2.6: The hardware reports a non fatal, correctable incidentoccured on CPU 0.Jesper Juhl
- Prev by Date: Re: stability problems with 2.4.24/Software RAID/ext3
- Next by Date: Re: Alt-arrow console switch sometimes dropped
- Previous by thread: Re: 2.6: The hardware reports a non fatal, correctable incidentoccured on CPU 0.
- Next by thread: Re: 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0.
- Indexes:[Main][Thread]