On Saturday 10 January 2004 00:12, Eric wrote: > Check your hardware CPU/MOBO/RAM. Overheating? Bad Ram? Cheap mobo? > MCE should not be triggered under any circumstances unless it is a kernel > bug(RARE, I believe the MCE code is simple) or you REALLY have a hardware > problem. As said before, the bios is resetting your fsb to 100 as a > fail-safe because something bad happened. Well, my system did run very stable and in the meantime again does run very stable on both, 2.4.21 and Windows XP... > BTW, check your setup, an AMD 2200+ should run at 1.8ghz i believe. If you Yes. > > What the fuck is going on here?? As far as I figured out this has > > something to do with MCE (CONFIG_X86_MCE=y, CONFIG_X86_MCE_NONFATAL=y) > > (?). > > Leave it enabled, its a good thing to tell you when you have bad hardware. > Its not a kernel problem, but a feature. Well, it is a good thing to tell me, but it's not a good thing to make my system auto-reset itself before reaching the BIOS afterwards... timo - 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/
Follow-Ups: 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 incident occured on CPU 0.Eric
- Prev by Date: 2.6.1 sound oops
- Next by Date: Re: [PATCH] First patch to improve ELF sanity checks
- Previous by thread: Re: 2.6: The hardware reports a non fatal, correctable incident occuredon CPU 0.
- Next by thread: Re: 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0.
- Indexes:[Main][Thread]