From owner-freebsd-hackers Thu Nov 14 7:36:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C53137B401; Thu, 14 Nov 2002 07:36:14 -0800 (PST) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4522A43E6E; Thu, 14 Nov 2002 07:36:13 -0800 (PST) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.6/8.12.5) with ESMTP id gAEFYlkY032719; Thu, 14 Nov 2002 10:34:47 -0500 (EST) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.6/8.12.5/Submit) with ESMTP id gAEFYkFo032716; Thu, 14 Nov 2002 10:34:47 -0500 (EST) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Thu, 14 Nov 2002 10:34:46 -0500 (EST) From: Kenneth Culver To: John Baldwin Cc: freebsd-hackers@FreeBSD.org Subject: RE: panic with nvidia drivers (but not sure it's nvidia's fault) In-Reply-To: <20021114102342.W32489-100000@alpha.yumyumyum.org> Message-ID: <20021114103213.D32489-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.9 required=5.0 tests=IN_REP_TO,X_AUTH_WARNING,NO_MX_FOR_FROM,AWL version=2.31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > several functions that call vm_object functions in FreeBSD's kernel that > eventually call atomic_clear_short(). For some reason those functions in > between aren't in the backtrace though, and without that I can (and > have) look through the code in the kernel to see how nv_alloc_pages can > get to atomic_clear_short through vm calls, but I'm not sure that's too > awefully helpful. Actually, after tracing through again, it appears to be following this codepath: (in reverse order from a backtrace) nv_alloc_pages() nv_free_vm_object() vm_object_deallocate() vm_object_clear_flag() atomic_clear_short() so I think it's possible that something may be getting screwed up between nv_free_vm_object and atomic_clear_short(). I'm not really sure how to tell though. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message