[PATCHv10 0/9] Xen: extend kexec hypercall for use with pv-ops kernels
daniel.kiper at oracle.com
Fri Nov 8 10:04:36 EST 2013
On Fri, Nov 08, 2013 at 01:13:59PM +0000, David Vrabel wrote:
> > (XEN) Domain 0 crashed: Executing crash image
> > gdb shows:
> > (gdb) bt
> > #0 0xffff82d0801a0092 in do_nmi_crash (regs=<optimized out>) at crash.c:113
> > #1 0xffff82d0802281d9 in nmi_crash () at entry.S:666
> > #2 0x0000000000000000 in ?? ()
> > (gdb)
> > Especially second bt line scares me... ;-)))
> > I have not been able to identify why NMI was activated because
> > stack is completely cleared.
> All this you have described here is correct and expected behavior,
> which, quite frankly, you should have been able to see with even the
> most cursory look at the code.
This is more a fun stuff than a real concern. That is why I have added
smile at the end of my statement. nmi_crash () at entry.S:666 is
a quite interesting coincidence for me... ;-)))
Anyway, it is interesting why all CPUs were stopped at this stage.
One should execute kdump code still. I will try to reproduce this
on real hardware.
More information about the kexec