Re: 2.6: The hardware reports a non fatal, correctable incidentoccured on CPU 0.

[Jesper Juhl <juhl-lkml _at_ xxxxxx>]

On Fri, 9 Jan 2004 lkml _at_ nitwit.de wrote:

> Hi!
>
> I did have some very scary issues today playing with 2.6. The system was
> booted and ran several times today, the longtest uptime was approximately
> about an hour.
>
> But then shortly after having booted 2.6 I got syslog messages:
>
> The hardware reports a non fatal, correctable incident occured on CPU 0.
>
> I shut down the machine. After this my Athlon XP 2200+ showed up as 1050MHz in
> BIOS an indeed the bus frequency was set to 100 instead of 133 MHz (how can
> an OS change the BIOS?!)

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.

The BIOS on my board will do that if the system fails to POST and I've
also seen it happen sometimes after a crash.

It's even documented in the motherboard manual that it will behave this
way when running in JumperFree mode (this is an ASUS A7M266 board btw).
The exact text from my motherboard manual is :

"Notes for JumperFree Mode
 System Hangup

 If your system crashes or hangs due to improper frequency settings, power
 OFF your system and restart. The system will start up in safe mode
 running at a DRAM-to-CPU frequency ratio of 3:3 and a bus speed of
 100MHz. You will then be led to BIOS setup to adjust the configurations."


-- 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/