Messages in this thread | | | Date | 6 Jul 2006 18:51:59 +0200 | Date | Thu, 6 Jul 2006 18:51:59 +0200 | From | Andi Kleen <> | Subject | Re: + edac-new-opteron-athlon64-memory-controller-driver.patch added to -mm tree |
| |
> With EDAC on my next boot I get positive confirmation that I either > pulled the DIMM that the error happened on, or I pulled a different > DIMM.
How? You simulate a new error and let EDAC resolve it?
> > Mapping the hardware addresses to the motherboard silk screen label > before hand is unnecessary and just ensures that you pull out the DIMM > you are trying for the first time. Making it an optimization for > people who do that a lot.
Sorry I didn't parse that.
> To the best of my knowledge mcelog even with the --dmi option cannot > give me that.
You mean identify if a given DIMM is still plugged in? You can get that information from dmidecode
-Andi - 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/
| |