Nvidia driver problems

From: Sascha Holzleiter <sascha_at_daemonground.de>
Date: 09 Jun 2003 23:22:55 +0200
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 _at_
/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 _at_
/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 _at_
/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 _at_
/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 _at_
/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 _at_
/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 _at_
/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 _at_
/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...
Received on Mon Jun 09 2003 - 12:23:00 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:11 UTC