From owner-freebsd-current@FreeBSD.ORG Fri Jun 15 19:32:20 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 4452116A41F for ; Fri, 15 Jun 2007 19:32:20 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0296013C4B0 for ; Fri, 15 Jun 2007 19:32:19 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l5FJ0vXj017571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Jun 2007 12:00:59 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4672E214.1030006@errno.com> Date: Fri, 15 Jun 2007 12:01:40 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.0 (X11/20070530) MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <1181929982.1086.6.camel@worf> <20070615203136.402a2df5.garyj@jennejohn.org> In-Reply-To: <20070615203136.402a2df5.garyj@jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, Pascal Hofstee 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 19:32:20 -0000 Gary Jennejohn wrote: > On Fri, 15 Jun 2007 19:53:02 +0200 > Pascal Hofstee wrote: > >> Sometime during the last week i have started to encounter trouble with >> my system locking up trying to switch from X to console, but only when >> using the nvidia-driver kernel module. Using the plain "nv" driver >> works without any problems ... When the lock up happens the system >> seems to no longer respond to keyboard input etc. (haven't been able >> to confirm wether or not remote access is still possible). >> >> Is anybody else experiencing similar problems out there ... this has >> used to work for months without problems ... i made sure to force a >> reinstall of the nvidia-driver port on every new kernel install but >> that just doesn't seem to solve the problem either. >> > > 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. > > BTW I tried _all_ versions of the driver and every one of them > exhibits this problem. > > I'm now using an old Matrox card via VGA (lost my DVI). I'm using: trouble% pkg_info|grep nvidia nvidia-driver-1.0.9631_5 NVidia graphics card binary drivers for hardware OpenGL ren w/o obvious issues on: nvidia0@pci1:0:0: class=0x030000 card=0x019010de chip=0x018a10de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'Quadro NVS with AGP 8X [NV18GL.2]' class = display subclass = VGA HEAD is: trouble% uname -a FreeBSD trouble.errno.com 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Sat Jun 2 21:33:05 PDT 2007 sam@stubby.errno.com:/usr/src/sys/i386/compile/STUBBY i386 I do not "switch from X to console". Sam