On Fri, May 06, 2011 at 10:24:12PM +0530, K.Prasad wrote: > Hi All, > I wanted to test the behaviour of kdump when panic is triggered > due to MCE on x86 and found that kdump is not captured. > > While the kdump service is configured and running and non-MCE panics > (such as those triggered through to /proc/sysrq-trigger) successfully > capture a kdump, any fatal MCE error injected through the mce-inject > tool causes a reboot of the machine. > > The code has been traced (using early_serial_putc()) to enter the kexec > path i.e. panic()->crash_kexec()->machine_kexec()->relocate_kernel() > but is untraceable further. > > Kdump works fine when the same the similar test is carried out inside a > KVM guest. > > Has anybody tested this before? Or have found kdump working when fatal > MCEs have actually occurred? 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
