From owner-freebsd-current@FreeBSD.ORG  Mon Jun  9 14:23:00 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 559FE37B401
	for <freebsd-current@freebsd.org>;
	Mon,  9 Jun 2003 14:23:00 -0700 (PDT)
Received: from mail.daemonground.de (daemonground.de [217.160.129.149])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 97CB143F3F
	for <freebsd-current@freebsd.org>;
	Mon,  9 Jun 2003 14:22:59 -0700 (PDT)
	(envelope-from sascha@daemonground.de)
Received: from dreamland.chief.home (p508397A6.dip.t-dialin.net
	[80.131.151.166])	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by mail.daemonground.de (Postfix) with ESMTP id 7822E880FE
	for <freebsd-current@freebsd.org>;
	Mon,  9 Jun 2003 23:22:57 +0200 (CEST)
From: Sascha Holzleiter <sascha@daemonground.de>
To: freebsd-current@freebsd.org
Content-Type: text/plain
Organization: 
Message-Id: <1055193775.7057.14.camel@dreamland.chief.home>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4 
Date: 09 Jun 2003 23:22:55 +0200
Content-Transfer-Encoding: 7bit
Subject: Nvidia driver problems
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2003 21:23:00 -0000

Hello,

just got these messages with a today -CURRENT and the nvidia driver
compiled with FREEBSD_AGP:

nvidia0: <GeForce4 Ti 4200> mem
0xf3800000-0xf387ffff,0xf4000000-0xf7ffffff,0xf1000000-0xf1ffffff irq 11
at device 0.0 on pci1
malloc() of "64" with the following non-sleepablelocks held:
exclusive sleep mutex dev.mtx_api r = 0 (0xc6b60b88) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711
malloc() of "VM OBJECT" with the following non-sleepablelocks held:
exclusive sleep mutex dev.mtx_api r = 0 (0xc6b60b88) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711
malloc() of "DP fakepg" with the following non-sleepablelocks held:
exclusive sleep mutex ctl.mtx_api r = 0 (0xc6cd74e8) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711
malloc() of "32" with the following non-sleepablelocks held:
exclusive sleep mutex dev.mtx_api r = 0 (0xc6b60b88) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711
malloc() of "4096" with the following non-sleepablelocks held:
exclusive sleep mutex dev.mtx_api r = 0 (0xc6b60b88) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711
malloc() of "32" with the following non-sleepablelocks held:
exclusive sleep mutex dev.mtx_api r = 0 (0xc6b60b88) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711
malloc() of "32768" with the following non-sleepablelocks held:
exclusive sleep mutex dev.mtx_api r = 0 (0xc6b60b88) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711
malloc() of "DP fakepg" with the following non-sleepablelocks held:
exclusive sleep mutex ctl.mtx_api r = 0 (0xc6cd74e8) locked @
/usr/ports/x11/nvidia-driver/work/NVIDIA_FreeBSD-1.0-3203/src/nvidia_subr.c:711

Is this just a "the nvidia driver isn't officially for the 5.x series"
issue or shouldn't this happen at all?

If I compile the module without FREEBSD_AGP and use it with the
debugging kernel the system core-dumps. Without debugging activated in
the kernel this is running quite stable...