>
> Neil, is it possible to do some serial console debugging to find out
> where exactly we are hanging? Beats me, what's that operation which can
> not be executed while being in NMI handler and makes system to hang. I am
> also curious to know if it is nested NMI case.
>
> Thanks
> Vivek
>
Hey-
Some intermediate results:
I've instrumented head.S in the kernel with the following code:
#define SEROUT(z) \
mov $0x3F8,%dx;\
movb z,%al;\
outb %dx
And peppered different ascii characters throughout the startup code from
startup_32 to right before the jump to start_kernel. When I panic the system
via an:
echo c > /proc/sysrq_trigger
I see an appropriate sequence of characters on the serial console
When I panic the box by forcing an NMI watchdog timeout however, I see nothing.
The machine will either hang, or reset into the bios. I think this is
reasonably conclusive in its indication that we're not getting into the second
kernel when this problem occurs. Next I'll instrument the purgatory code in a
simmilar way.
Regards
Neil
> _______________________________________________
> kexec mailing list
> [EMAIL PROTECTED]
> http://lists.infradead.org/mailman/listinfo/kexec
--
/****************************************************
* Neil Horman <[EMAIL PROTECTED]>
* Software Engineer, Red Hat
****************************************************/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
