Hi,<br> Yes. I was trying to get coredump on virtual box and added extra virtual CPU to the guest virtual machine.<br><br>Regards,<br>Neha<br><br><div class="gmail_quote">On Mon, Aug 5, 2013 at 12:44 PM, Vivek Satpute <span dir="ltr"><<a href="mailto:vivekonline86@gmail.com" target="_blank">vivekonline86@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Neha,<br>
<br>
Are you trying to get coredump on virtual box and added extra virtual<br>
CPU to that guest virtual machine ?<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Vivek<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Sat, Aug 3, 2013 at 10:48 AM, anish singh<br>
<<a href="mailto:anish198519851985@gmail.com">anish198519851985@gmail.com</a>> wrote:<br>
><br>
> On Aug 3, 2013 3:02 AM, "neha naik" <<a href="mailto:nehanaik27@gmail.com">nehanaik27@gmail.com</a>> wrote:<br>
>><br>
>> Hi All,<br>
>> I looked into my issue and i had only one cpu on that machine and i was<br>
>> getting messages like process # waiting for # secs.<br>
>> My theory is that this process was of doing some kind of busy looping on<br>
>> 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<br>
>> posting this<br>
> How did you do that?How can you limit the number of cpus?I wonder if there<br>
> is some sysfs control for that?<br>
><br>
> because someone else may find it useful.<br>
>><br>
>> Regards,<br>
>> Neha<br>
>><br>
>> On Thu, May 30, 2013 at 11:44 AM, <<a href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</a>> wrote:<br>
>>><br>
>>> 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<br>
>>> > 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<br>
>>> > gone<br>
>>> > into such a state that it cannot even follow the procedure for<br>
>>> > crash dump.<br>
>>><br>
>>> 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>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Kernelnewbies mailing list<br>
>> <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
>> <a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Kernelnewbies mailing list<br>
> <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
> <a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
><br>
</div></div></blockquote></div><br>