Debug: sleeping function called from invalid context at...

[vasyl83]

everytime I boot gentoo I get this in my dmesg,
Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
[<c011b30b>] __might_sleep+0xab/0xd0
[<c016ab26>] alloc_inode+0x146/0x150
[<c013d885>] kmem_cache_alloc+0x65/0x70
[<c014c141>] __get_vm_area+0x21/0x100
[<c014c253>] get_vm_area+0x33/0x40
[<c0118613>] __ioremap+0xb3/0x100
[<c0118689>] ioremap_nocache+0x29/0xb0
[<d1b9647e>] os_map_kernel_space+0x68/0x6c [nvidia]
[<d1ba8a77>] __nvsym00568+0x1f/0x2c [nvidia]
[<d1baab96>] __nvsym00775+0x6e/0xe0 [nvidia]
[<d1baac26>] __nvsym00781+0x1e/0x190 [nvidia]
[<d1bac6ac>] rm_init_adapter+0xc/0x10 [nvidia]
[<d1b92ee0>] nv_kern_open+0xf5/0x232 [nvidia]
[<c015ad04>] chrdev_open+0xf4/0x220
[<c01b6b11>] devfs_open+0xe1/0xf0
[<c0150c71>] dentry_open+0x151/0x220
[<c0150b16>] filp_open+0x66/0x70
[<c0150fb3>] sys_open+0x53/0x90
[<c010934b>] syscall_call+0x7/0xb

Ive seen similar error while googling but they all had different call traces. What can be causing it?

[ckdake]

This is from having "Sleep-inside-spinlock-checking" being enabled in your kernel config inside of the "kernel hacking" section. Turn it off and the error message should magically disappear.
_________________
http://ckdake.com/