Date: Fri, 15 Jun 2007 16:09:17 -0400 From: Adam K Kirchhoff <adamk@voicenet.com> To: Craig Rodrigues <rodrigc@crodrigues.org> Cc: Pascal Hofstee <caelian@gmail.com>, gary.jennejohn@freenet.de, current@freebsd.org Subject: Re: recent nvidia-driver trouble Message-ID: <1181938157.11238.0.camel@sorrow> In-Reply-To: <20070615190107.GA2111@crodrigues.org> References: <1181929982.1086.6.camel@worf> <20070615203136.402a2df5.garyj@jennejohn.org> <20070615190107.GA2111@crodrigues.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2007-06-15 at 15:01 -0400, Craig Rodrigues wrote: > On Fri, Jun 15, 2007 at 08:31:36PM +0200, Gary Jennejohn wrote: > > I've seen this also. It's a panic due to a NULL-pointer dereference > > someplace in the nvidia-driver. I suspect that it's related to the > > recent locking/mutex/whatever changes but can't prove it. All the > > crash dumps which I have are corrupted so I can't do a backtrace :-( > > > > The bug seems to be in the binary blob part of the driver, which means > > we have to wait for Nvidia to get around to fixing it. > > Have you reported this problem to Nvidia? They don't regularly > monitor FreeBSD mailing lists, but I've found that they > are fairly responsive to e-mails sent to: > freebsd-gfx-bugs@nvidia.com > They do regularly monitor this forum: http://www.nvnews.net/vbulletin/forumdisplay.php?f=47 When there was a problem with the device cloning, I mentioned it there, and they had a patch available in the next few days, iirc. Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1181938157.11238.0.camel>