Date: Tue, 04 Mar 2003 08:15:20 -0700 From: Scott Long <scott_long@btc.adaptec.com> To: Maxime Henrion <mux@freebsd.org> Cc: walt <wa1ter@myrealbox.com>, freebsd-current@freebsd.org Subject: Re: nvidia module panics today's kernel [03-03-03] Message-ID: <3E64C308.4060904@btc.adaptec.com> In-Reply-To: <20030304143536.GA63673@elvis.mu.org> References: <3E64335A.60408@myrealbox.com> <20030304143536.GA63673@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxime Henrion wrote: > walt wrote: > >>My mini 'disaster' of earlier today was caused by the nvidia kernel >>module being autoloaded at boot, which causes an immediate kernel panic. >> >>The newest kernel seems fine until I try to load the module manually, >>at which time I still get the kernel panic even after re-compiling >>the module. >> >>Maxime, it looks like the nvidia module will need to be sculpted one >>more time. :-( > > > Yes, the cdevsw initialization scheme and the driver needs to be updated > accordingly. I've updated my patch at : > > http://mu.org/~mux/patches/nvidia.patch > > Cheers, > Maxime > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Maybe the kernel driver portion of the nvidia driver set should be imported into /sys/contrib? It seems to be breaking quite often at the hands of people who usually are good about updating all drivers in the tree. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E64C308.4060904>