On Wed, Oct 13, 2010 at 11:54 PM, Amit Nagal <helloin.amit@xxxxxxxxx> wrote: > Hi , > > i am getting this kernel log . > > BUG: sleeping function called from invalid context at mm/slab.c:3055 > in_atomic(): 1, irqs_disabled(): 128, pid: 192, name: Front Display > Backtrace: > [<c002cf94>] (dump_backtrace+0x0/0x110) from [<c02fb048>] (dump_stack+0x18/0x1c) > r6:c40000c0 r5:000000d0 r4:c41f1160 r3:40000093 > [<c02fb030>] (dump_stack+0x0/0x1c) from [<c004cf08>] (__might_sleep+0x108/0x128) > [<c004ce00>] (__might_sleep+0x0/0x128) from [<c00ccfd0>] > (kmem_cache_alloc+0x30/0x148) > [<c00ccfa0>] (kmem_cache_alloc+0x0/0x148) from [<bf0edf80>] > (spi_write+0x29c/0x4d4 [fpi]) > r8:80000013 r7:83bd8d08 r6:a0000013 r5:00000004 r4:c41f1160 > [<bf0edce4>] (spi_write+0x0/0x4d4 [fpi]) from [<c00d1498>] > (vfs_write+0xb4/0x128) > [<c00d13e4>] (vfs_write+0x0/0x128) from [<c00d15d4>] (sys_write+0x44/0x70) > r6:00000004 r5:83bd8d08 r4:c1000a60 r3:c77adf70 > [<c00d1590>] (sys_write+0x0/0x70) from [<c0028980>] (ret_fast_syscall+0x0/0x2c) > r9:c77ac000 r8:c0028b28 r6:02b90784 r5:00000004 r4:83bd8d08 > > > can anybody guide me what is meant by this bug : The code was trying to allocate memory while holding a spin lock or some other scenario where you cannot be sleep (ex. interrupt handlers or bottom halves which doesn't appear to be the case here). Using GFP_NOWAIT or GFP_ATOMIC flag in kmem_cache_alloc(..) call should fix the issue Venkatram Tummala > > BUG: sleeping function called from invalid context at mm/slab.c:3055 > > and what kernel functions it points to where problem lies . > > Thanx & Regards > Amit > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
