Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264333AbTKUIfz (ORCPT ); Fri, 21 Nov 2003 03:35:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264334AbTKUIfz (ORCPT ); Fri, 21 Nov 2003 03:35:55 -0500 Received: from fw.osdl.org ([65.172.181.6]:50371 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S264333AbTKUIfw (ORCPT ); Fri, 21 Nov 2003 03:35:52 -0500 Date: Fri, 21 Nov 2003 00:41:33 -0800 From: Andrew Morton To: "Prakash K. Cheemplavam" Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.0-test9-mm4 Message-Id: <20031121004133.1a111786.akpm@osdl.org> In-Reply-To: <3FBDCCDF.9010304@gmx.de> References: <20031118225120.1d213db2.akpm@osdl.org> <3FBDCCDF.9010304@gmx.de> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1355 Lines: 33 "Prakash K. Cheemplavam" 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: > [] __might_sleep+0xab/0xd0 > [] kmem_cache_alloc+0x65/0x70 > [] __get_vm_area+0x21/0xf0 > [] get_vm_area+0x33/0x40 > [] __ioremap+0xb3/0x100 > [] ioremap_nocache+0x29/0xb0 > [] os_map_kernel_space+0x68/0x6c [nvidia] > [] __nvsym00568+0x1f/0x2c [nvidia] > [] __nvsym00775+0x6e/0xe0 [nvidia] > [] __nvsym00781+0x1e/0x190 [nvidia] > [] rm_init_adapter+0xc/0x10 [nvidia] > [] nv_kern_open+0xf3/0x228 [nvidia] > [] exact_match+0x0/0x10 > [] chrdev_open+0xf1/0x220 > [] devfs_open+0xe2/0xf0 > [] dentry_open+0x152/0x270 > [] filp_open+0x5b/0x60 > [] sys_open+0x53/0x90 > [] sysenter_past_esp+0x43/0x65 That would be a locking error in the nvidia driver. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/