Hi All,<br> I looked into my issue and i had only one cpu on that machine and i was getting messages like process # waiting for # secs.<br> My theory is that this process was of doing some kind of busy looping on that cpu so that the operating system could<br>
not even generate a dump.<br> The moment i increased the number of cpus i got the dump. I am just posting this because someone else may find it useful.<br><br>Regards,<br>Neha<br><br><div class="gmail_quote">On Thu, May 30, 2013 at 11:44 AM, <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, 30 May 2013 11:31:49 -0600, neha naik said:<br>
<br>
> I have loaded the linux crashdump on ubuntu machine. I can manually<br>
> generate the crashdump by the 'echo c > /proc/sysrq-trigger'.<br>
> However, i am having a panic in a module i have written, which is not<br>
> generating a core dump. I simply see the stack in the console and it kind of<br>
> hangs there. I have to manually power it off and power it on ...<br>
> Can someone explain why this happens? Is it because the kernel has gone<br>
> into such a state that it cannot even follow the procedure for<br>
> crash dump.<br>
<br>
</div></div>Most likely, your module isn't in fact panic'ing, but oops'ing.<br>
There's a number of kernel variables that control whether to panic.<br>
<br>
ls -l /proc/sys/kernel/*panic*<br>
<br>
and for example 'echo 1 > /proc/sys/kernel/panic_on_oops' will cause<br>
a panic if something oops'es.<br>
</blockquote></div><br>