Hello Balbir,Hey, I see something similar and I actually have a stack trace. Here it goes: bash[498] segfault at ffffffff80868b58 ip ffffffffff600412 sp 7fffa3d010f0 error 7 init[1] segfault at ffffffff80868b58 ip ffffffffff600412 sp 7fff9e97f640 error 7 init[1] segfault at ffffffff80868b58 ip ffffffffff600412 sp 7fff9e97eed0 error 7 Kernel panic - not syncing: Attemted to kill init! Pid 1, comm: init Not tainted 2.6.26-rc5-mm1 #1 Call Trace: [<ffffffff80254632>] panic+0xe2/0x260 [<ffffffff802fa8ba>] ? __slab_free+0x10a/0x630 [<ffffffff80265a8e>] ? __sigqueue_free+0x5e/0x70 [<ffffffff802851eb>] ? trace_hardirqs_off+0x1b/0x30 [<ffffffff802851eb>] ? trace_hardirqs_off+0x1b/0x30 [<ffffffff80259b54>] do_exit+0xb84/0xc30 [<ffffffff80259c5a>] do_group_exit+0x5a/0x110 [<ffffffff8026a3b5>] get_signal_to_deliver+0x2c5/0x620 [<ffffffff8020bb3b>] do_notify_resume+0x11b/0xd10 [<ffffffff8028da5b>] ? trace_hardirqs_on+0x1b/0x30 [<ffffffff805cd0f3>] ? _spin_unlock_irqrestore+0x93/0x130 [<ffffffff8026865c>] ? force_sig_info+0x10c/0x130 [<ffffffff8022fb9c>] ? force_sig_info_fault+0x2c/0x40 [<ffffffff802dd7dd>] ? print_vma_addr+0x10d/0x1d0 [<ffffffff805cbb67>] ? trace_hardirqs_on_thunk+0x3a/0x3f [<ffffffff8028d8da>] ? trace_hardirqs_on_caller+0x15a/0x2c0 [<ffffffff8020d4c9>] retint_signal+0x46/0x8d This was copied manually so typos are possible. Mariusz --
