From owner-freebsd-current@FreeBSD.ORG  Fri Sep 21 21:55:25 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A71EA16A41A
	for <current@freebsd.org>; Fri, 21 Sep 2007 21:55:25 +0000 (UTC)
	(envelope-from cb@severious.net)
Received: from ion.gank.org (ion.gank.org [69.55.238.164])
	by mx1.freebsd.org (Postfix) with ESMTP id 9645413C478
	for <current@freebsd.org>; Fri, 21 Sep 2007 21:55:25 +0000 (UTC)
	(envelope-from cb@severious.net)
Received: by ion.gank.org (Postfix, from userid 1001)
	id 5DE1D10F44; Fri, 21 Sep 2007 16:55:25 -0500 (CDT)
Date: Fri, 21 Sep 2007 16:55:24 -0500
From: Craig Boston <cb@severious.net>
To: current@freebsd.org
Message-ID: <20070921215514.GA1114@nowhere>
Mail-Followup-To: Craig Boston <cb@severious.net>, current@freebsd.org
References: <20070921202523.GB4044@nowhere>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070921202523.GB4044@nowhere>
User-Agent: Mutt/1.4.2.3i
Cc: 
Subject: Re: nvidia driver on recent current?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2007 21:55:25 -0000

On Fri, Sep 21, 2007 at 03:25:24PM -0500, Craig Boston wrote:
> Some of the addresses look very suspicious, so it seems the stack is
> likely corrupted.

Now that I think about it, the stack isn't corrupt.  Those are just the
arguments for the ?? functions that kgdb can't work out the prototype
for.

A little extra info, this is the newest nvidia driver -- 100.14.11.  It
happens on a kernel from last week, as well as an 8/31 build that I
tried rolling back to.  Before that it was stable for months, but as
it's somewhat intermittent it may take a while to locate the exact
change.  Running multiple GL clients at once seems to be a good way, and
it almost always happens just as one terminates.

This is an SMP system.  I habitually add -DKSE -DSMP to the nvidia
driver CFLAGS between the 'make patch' and 'make build' steps in the
port install, but taking those out doesn't seem to have any effect.

Craig