[Bug] Kdump does not work when panic triggered due to MCE
vgoyal at redhat.com
Mon May 9 11:46:06 EDT 2011
On Mon, May 09, 2011 at 05:21:06PM +0200, Bouchard Louis wrote:
> Le 09/05/2011 14:39, Vivek Goyal a écrit :
> > Prasad,
> > I have never tried taking dump in MCE situation. Does kdump work on this
> > machine with normal panic()?
> > Use --debug and --serial option in kexec-tools to print some debug message
> > and look for "I am in purgatory". This will tell you whether you hanged
> > in first kernel or second kernel.
> > Then put "outb()" messages in the kernel to trace what happened.
> > Thanks
> > Vivek
> > _______________________________________________
> > kexec mailing list
> > kexec at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/kexec
> I have seen numerous occurrences of MCE triggered kernel panics on both
> RHEL & SLES environment used on IA32 architecture. Both in contexts
> where kexec/kdump was being used.
> Matter of fact, MCE triggered panic are part of the reason that pushed
> me to work on crashdc : only one crash command is required to get the
> MCE trace out of the kernel ring buffer. This avoids transfering massive
> amount of vmcore file over the net.
> crashdc does well on those, mcelog can be applied on the data gathered.
Louis, is this "crashdc" an independent executable. Where is it packaged?
What is the significance of name "crashdc" (Crash data collecor ?) Will it
make sense to merge it with makedumpfile which does kernel filtering
already and this could be one of the additional features.
> Louis Bouchard
> Server Support Analyst
> Canonical Ltd
> Ubuntu support: http://landscape.canonical.com
More information about the kexec