Re: BUG: sleeping function called from invalid context at mm/slab.c
On Wed, Oct 13, 2010 at 11:54 PM, Amit Nagal 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: > [] (dump_backtrace+0x0/0x110) from [] > (dump_stack+0x18/0x1c) > r6:c4c0 r5:00d0 r4:c41f1160 r3:4093 > [] (dump_stack+0x0/0x1c) from [] > (__might_sleep+0x108/0x128) > [] (__might_sleep+0x0/0x128) from [] > (kmem_cache_alloc+0x30/0x148) > [] (kmem_cache_alloc+0x0/0x148) from [] > (spi_write+0x29c/0x4d4 [fpi]) > r8:8013 r7:83bd8d08 r6:a013 r5:0004 r4:c41f1160 > [] (spi_write+0x0/0x4d4 [fpi]) from [] > (vfs_write+0xb4/0x128) > [] (vfs_write+0x0/0x128) from [] (sys_write+0x44/0x70) > r6:0004 r5:83bd8d08 r4:c1000a60 r3:c77adf70 > [] (sys_write+0x0/0x70) from [] > (ret_fast_syscall+0x0/0x2c) > r9:c77ac000 r8:c0028b28 r6:02b90784 r5:0004 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 ecar...@nl.linux.org > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
Re: BUG: sleeping function called from invalid context at mm/slab.c
On Wed, Oct 13, 2010 at 11:54 PM, Amit Nagal 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: > [] (dump_backtrace+0x0/0x110) from [] > (dump_stack+0x18/0x1c) > r6:c4c0 r5:00d0 r4:c41f1160 r3:4093 > [] (dump_stack+0x0/0x1c) from [] > (__might_sleep+0x108/0x128) > [] (__might_sleep+0x0/0x128) from [] > (kmem_cache_alloc+0x30/0x148) > [] (kmem_cache_alloc+0x0/0x148) from [] > (spi_write+0x29c/0x4d4 [fpi]) I guess the interesting part is "spi_write+0x0/0x4d4 ". Looks like it is trying to do some memory allocation from the place where it is not supposed to do ie... where the code isn't expected to sleep. > r8:8013 r7:83bd8d08 r6:a013 r5:0004 r4:c41f1160 > [] (spi_write+0x0/0x4d4 [fpi]) from [] > (vfs_write+0xb4/0x128) > [] (vfs_write+0x0/0x128) from [] (sys_write+0x44/0x70) > r6:0004 r5:83bd8d08 r4:c1000a60 r3:c77adf70 > [] (sys_write+0x0/0x70) from [] > (ret_fast_syscall+0x0/0x2c) > r9:c77ac000 r8:c0028b28 r6:02b90784 r5:0004 r4:83bd8d08 > > > can anybody guide me what is meant by this bug : > > 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 ecar...@nl.linux.org > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- Thanks - Manish == [$\*.^ -- I miss being one of them == -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
Re: BUG: sleeping function called from invalid context at mm/slab.c
1) linux kernel version 2.6.30.9 2) this happens while doing digital audio streaming over usb interface on usb host . also that time timing information also gets updated on the embedded target's front display simultaneously . regards Amit On Thu, Oct 14, 2010 at 12:59 PM, Prasad Joshi wrote: > Could you please describe when did this happen? > Also paste the output of the command uname -a > > On Thu, Oct 14, 2010 at 12:24 PM, Amit Nagal 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: >> [] (dump_backtrace+0x0/0x110) from [] >> (dump_stack+0x18/0x1c) >> r6:c4c0 r5:00d0 r4:c41f1160 r3:4093 >> [] (dump_stack+0x0/0x1c) from [] >> (__might_sleep+0x108/0x128) >> [] (__might_sleep+0x0/0x128) from [] >> (kmem_cache_alloc+0x30/0x148) >> [] (kmem_cache_alloc+0x0/0x148) from [] >> (spi_write+0x29c/0x4d4 [fpi]) >> r8:8013 r7:83bd8d08 r6:a013 r5:0004 r4:c41f1160 >> [] (spi_write+0x0/0x4d4 [fpi]) from [] >> (vfs_write+0xb4/0x128) >> [] (vfs_write+0x0/0x128) from [] (sys_write+0x44/0x70) >> r6:0004 r5:83bd8d08 r4:c1000a60 r3:c77adf70 >> [] (sys_write+0x0/0x70) from [] >> (ret_fast_syscall+0x0/0x2c) >> r9:c77ac000 r8:c0028b28 r6:02b90784 r5:0004 r4:83bd8d08 >> >> >> can anybody guide me what is meant by this bug : >> >> 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 ecar...@nl.linux.org >> Please read the FAQ at http://kernelnewbies.org/FAQ >> >> > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
Re: BUG: sleeping function called from invalid context at mm/slab.c
Could you please describe when did this happen? Also paste the output of the command uname -a On Thu, Oct 14, 2010 at 12:24 PM, Amit Nagal 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: > [] (dump_backtrace+0x0/0x110) from [] > (dump_stack+0x18/0x1c) > r6:c4c0 r5:00d0 r4:c41f1160 r3:4093 > [] (dump_stack+0x0/0x1c) from [] > (__might_sleep+0x108/0x128) > [] (__might_sleep+0x0/0x128) from [] > (kmem_cache_alloc+0x30/0x148) > [] (kmem_cache_alloc+0x0/0x148) from [] > (spi_write+0x29c/0x4d4 [fpi]) > r8:8013 r7:83bd8d08 r6:a013 r5:0004 r4:c41f1160 > [] (spi_write+0x0/0x4d4 [fpi]) from [] > (vfs_write+0xb4/0x128) > [] (vfs_write+0x0/0x128) from [] (sys_write+0x44/0x70) > r6:0004 r5:83bd8d08 r4:c1000a60 r3:c77adf70 > [] (sys_write+0x0/0x70) from [] > (ret_fast_syscall+0x0/0x2c) > r9:c77ac000 r8:c0028b28 r6:02b90784 r5:0004 r4:83bd8d08 > > > can anybody guide me what is meant by this bug : > > 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 ecar...@nl.linux.org > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
BUG: sleeping function called from invalid context at mm/slab.c
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: [] (dump_backtrace+0x0/0x110) from [] (dump_stack+0x18/0x1c) r6:c4c0 r5:00d0 r4:c41f1160 r3:4093 [] (dump_stack+0x0/0x1c) from [] (__might_sleep+0x108/0x128) [] (__might_sleep+0x0/0x128) from [] (kmem_cache_alloc+0x30/0x148) [] (kmem_cache_alloc+0x0/0x148) from [] (spi_write+0x29c/0x4d4 [fpi]) r8:8013 r7:83bd8d08 r6:a013 r5:0004 r4:c41f1160 [] (spi_write+0x0/0x4d4 [fpi]) from [] (vfs_write+0xb4/0x128) [] (vfs_write+0x0/0x128) from [] (sys_write+0x44/0x70) r6:0004 r5:83bd8d08 r4:c1000a60 r3:c77adf70 [] (sys_write+0x0/0x70) from [] (ret_fast_syscall+0x0/0x2c) r9:c77ac000 r8:c0028b28 r6:02b90784 r5:0004 r4:83bd8d08 can anybody guide me what is meant by this bug : 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 ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
