Hi,

I have a custom linux kernel version 2.6.32 running as a VM on Hyper-V 2008 R2 with 2vCPUs.

When I am triggering kdump using the magic sysrq (sh#echo c > /proc/sysrq-trigger), the VM gets rebooted in the middle of starting the capture kernel. This happens intermittently with no reason for the reboot. The Windows eventlog shows it is a CPU triple fault issue.

But, when I trigger kdump after entering in to kernel kdb mode (kdb#kdump), kdump is working successfully for multiple times.

So, what is the difference between the two methods? Is there any interrupt which is not properly handle in sysrq kdump ?
Please explain ?

Thanks in advance,
Saleem

Hello experts,

Could someone answer this?

Thanks,
Saleem