<br><br><div class="gmail_quote">On Fri, Mar 14, 2008 at 4:52 PM, Mohan Kumar M <<a href="mailto:mohan@in.ibm.com">mohan@in.ibm.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Mar 14, 2008 at 04:18:52AM -0700, Rajasekaran P wrote:<br>
> Yes,I built this kernel with CRASH_DUMP and VMCORE file system enabled.<br>
> Moreover, I disabled SMP as well.<br>
> My system kernel is (First kernel) is SMP enabled, does it matter?<br>
<br>
</div>It should not matter.<br>
<div class="Ih2E3d"><br>
><br>
> I dont get any message from dump capture kernel.<br>
><br>
> I trigger crash dump using :<br>
><br>
> echo c > /proc/sysrq-trigger<br>
<br>
</div>While triggering the dump, don't you get any message, like sending IPI<br>
to cpu?<br>
<div class="Ih2E3d"></div></blockquote><div><br>No, I dont get anything on terminal.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> Initially capture kernel was loaded into 32MB only, but still it was not<br>
> booting. So I tweaked the KDUMP_KERNELBASE macro to load capture kernel to<br>
> 64MB ( My idea is, first 64MB for system kernel and second 64MB for capture<br>
> kernel). Should it be 32MB only?<br>
<br>
</div>You can't do that. It should be at 32MB only.</blockquote><div>Ok, I will try this and update. <br></div></div><br>