On Fri, Oct 07, 2011 at 09:42:19PM +0530, K.Prasad wrote:
> The problem, as pointed out by Borislav Petkov in a different mail, is that
> we might end up capturing a vmcore containing corrupted data when the
> same is not required for analysing the cause of the crash.
>
> Of course, all this is assuming that reading the faulty memory with MCE
> disabled is harmless. However, the effect of a read operation in this
> case is undefined.
Frankly, I don't think that it is undefined - you basically should be
able to read DRAM albeit with the corrupted data in it. However, you
probably best disable the whole DRAM error detection first by clearing
a couple of bits in MC4_CTL_MASK (at least on AMD that should work, I
dunno how Intel does that).
But, regardless, according to Vivek, the "makedumpfile" tool should be
able to jump over poisoned pages and you don't need all the hoopla above
at all, right?
Thanks.
--
Regards/Gruss,
Boris.
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
