Yes,<br><br>You are right. CONFIG_PREEMPT is enabled in the kernel config.<br><br>Attached is the config.<br><br>Thanks<br>-Srikanth<br><br><br><div class="gmail_quote">On Thu, Aug 6, 2009 at 7:56 PM, Josh Boyer <span dir="ltr"><<a href="mailto:jwboyer@linux.vnet.ibm.com">jwboyer@linux.vnet.ibm.com</a>></span> 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="im">On Thu, Aug 06, 2009 at 06:46:26PM +0530, srikanth krishnakar wrote:<br>
>Hi all,<br>
><br>
>Here is kernel bug for linux-2.6.29.6 for PowerPC (ppc440) target, while<br>
>running ipsec application it is observed that kernel oops'es oftenly as show<br>
>below :<br>
><br>
>root@powerpc:~# ./ipsec<br>
>------------[ cut here ]------------<br>
>kernel BUG at mm/slab.c:3002!<br>
>Oops: Exception in kernel mode, sig: 5 [#1]<br>
>PREEMPT LTT NESTING LEVEL : 0<br>
<br>
</div>LTT?<br>
<div class="im"><br>
>Any Clue or any bugs found in mm/slab.c for linux-2.6.29.6 while<br>
>running IPSEC applications ?<br>
<br>
</div>Do you have CONFIG_PREEMPT set? The oops output seems to think so. Also,<br>
seeing the LTT makes me wonder if you have added custom patches to your kernel?<br>
<br>
Do you have a simple testcase that could be run to recreate this? If so,<br>
could you provide it somewhere and perhaps your .config?<br>
<font color="#888888"><br>
josh<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>"The Good You Do, The Best You GET"<br><br>Regards<br>Srikanth Krishnakar<br>**********************<br>