Re: 2.6.0-test9-mm4

[Prakash K. Cheemplavam]

Andrew Morton wrote:
> "Prakash K. Cheemplavam" <prakashpublic@xxxxxx> wrote:
>
> > DMESG gives me following:
> >
> > Debug: sleeping function called from invalid context at mm/slab.c:1868
> > in_atomic():1, irqs_disabled():0
> > Call Trace:
> >   [<c0120fbb>] __might_sleep+0xab/0xd0
> >   [<c0144fa5>] kmem_cache_alloc+0x65/0x70
> >   [<c0155161>] __get_vm_area+0x21/0xf0
> >   [<c0155263>] get_vm_area+0x33/0x40
> >   [<c011df03>] __ioremap+0xb3/0x100
> >   [<c011df79>] ioremap_nocache+0x29/0xb0
> >   [<f9a5ad87>] os_map_kernel_space+0x68/0x6c [nvidia]
> >   [<f9a6d377>] __nvsym00568+0x1f/0x2c [nvidia]
> >   [<f9a6f496>] __nvsym00775+0x6e/0xe0 [nvidia]
> >   [<f9a6f526>] __nvsym00781+0x1e/0x190 [nvidia]
> >   [<f9a70fac>] rm_init_adapter+0xc/0x10 [nvidia]
> >   [<f9a57dc9>] nv_kern_open+0xf3/0x228 [nvidia]
> >   [<c0164b40>] exact_match+0x0/0x10
> >   [<c0164941>] chrdev_open+0xf1/0x220
> >   [<c01aa332>] devfs_open+0xe2/0xf0
> >   [<c0159f32>] dentry_open+0x152/0x270
> >   [<c0159ddb>] filp_open+0x5b/0x60
> >   [<c015a2c3>] sys_open+0x53/0x90
> >   [<c041f532>] sysenter_past_esp+0x43/0x65
>
>
> That would be a locking error in the nvidia driver.

What does that mean and how to get rid of it?

Prakash

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/