Josh Brooks wrote:
> Understood. Thank you for that diagnosis.
>
> usually it says proc #1 in the error, but the first time it said proc #0 -
> is that interesting ?
It is.
This would be a stronger evidence of bad RAM, since the instruction
fetch error occured "randomly" on both processors.
Either that or both your processors are going bad :)
Please run memtest86 to be sure it's a bad RAM problem.
Kind Regards,
Felipe
-
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/
This archive was generated by hypermail 2b29 : Tue Dec 31 2002 - 22:00:08 EST