Hi... On Thu, Dec 23, 2010 at 04:44, Sengottuvelan S <sengottuvelan.s@xxxxxxxxx> wrote: > comm "insmod", pid 1559, jiffies 4294961804 (age 229.610s) > hex dump (first 32 bytes): > fa 3e 00 00 00 00 00 00 92 5a 00 00 00 00 00 00 .>.......Z...... > 0a 00 00 00 12 00 00 00 3c 38 00 00 00 00 00 00 ........<8...... > backtrace: > [<ffffffff8156eb1d>] kmemleak_alloc+0x2d/0x60 > [<ffffffff81152469>] __vmalloc_node+0xc9/0xe0 > [<ffffffff8115280c>] vmalloc+0x2c/0x30 > [<ffffffffa0099047>] 0xffffffffa0099047 > [<ffffffffa009906c>] 0xffffffffa009906c > [<ffffffff8100204c>] do_one_initcall+0x3c/0x1a0 > [<ffffffff810cea1b>] sys_init_module+0xbb/0x200 > [<ffffffff81041072>] system_call_fastpath+0x16/0x1b > [<ffffffffffffffff>] 0xffffffffffffffff Fairly likely, it's either: a. Stack frame is corrupted or b. the area isn't so near of any recorded symbol -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
