From owner-freebsd-current@FreeBSD.ORG Fri Jun 15 20:28:01 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F77016A468 for ; Fri, 15 Jun 2007 20:28:01 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from b.mx.visualtech.com (imap.visualtech.com [208.16.19.9]) by mx1.freebsd.org (Postfix) with ESMTP id 45E6213C448 for ; Fri, 15 Jun 2007 20:28:01 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from [192.168.0.101] (c-68-45-180-45.hsd1.nj.comcast.net [68.45.180.45]) by b.mx.visualtech.com (Postfix) with ESMTP id B02CE48410; Fri, 15 Jun 2007 16:09:19 -0400 (EDT) From: Adam K Kirchhoff To: Craig Rodrigues In-Reply-To: <20070615190107.GA2111@crodrigues.org> References: <1181929982.1086.6.camel@worf> <20070615203136.402a2df5.garyj@jennejohn.org> <20070615190107.GA2111@crodrigues.org> Content-Type: text/plain Date: Fri, 15 Jun 2007 16:09:17 -0400 Message-Id: <1181938157.11238.0.camel@sorrow> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Cc: Pascal Hofstee , gary.jennejohn@freenet.de, current@freebsd.org Subject: Re: recent nvidia-driver trouble X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2007 20:28:01 -0000 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