From owner-freebsd-amd64@freebsd.org  Wed Jan  6 01:12:46 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D1B4A6364D
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed,  6 Jan 2016 01:12:46 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1DEDD1A8F
 for <freebsd-amd64@FreeBSD.org>; Wed,  6 Jan 2016 01:12:46 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u061Cjn8082355
 for <freebsd-amd64@FreeBSD.org>; Wed, 6 Jan 2016 01:12:45 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 205903] x11/nvidia-driver-340: Repeating crash with
 nvidia-driver: "fault on nofault entry"
Date: Wed, 06 Jan 2016 01:12:45 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: aritger@nvidia.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: danfe@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-205903-6-Ytf2tU0Rhg@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205903-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-205903-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 06 Jan 2016 02:37:47 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 01:12:46 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205903

Andy Ritger <aritger@nvidia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aritger@nvidia.com

--- Comment #3 from Andy Ritger <aritger@nvidia.com> ---
So far from the stack trace, it looks like a process (vimb) using a user-mo=
de
nvidia driver component (OpenGL?) was killed due to running out of swap,
nvidia.ko attempted to clean up after that process, and somehow confused it=
self
over resources that had been allocated for that user-mode nvidia driver
component.

Michael: are you able to trigger this on demand by manually killing vimb, or
does it require running out of swap and inducing the out-of-memory killer?

340.96 is a relatively old NVIDIA driver version.  Could you test with
something more recent?  E.g., either of these:

http://www.nvidia.com/Download/driverResults.aspx/95925/en-us
http://www.nvidia.com/Download/driverResults.aspx/95163/en-us

Thanks.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=