Date: Fri, 20 May 2016 07:05:04 +0000 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" Message-ID: <bug-205903-6-xn17doHEnH@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205903 --- Comment #9 from Michael Danilov <mike.d.ft402@gmail.com> --- Created attachment 170497 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D170497&action= =3Dedit Patch to x11/nvidia-driver to CAUSE the panic. Alright, I think I have come up with a reliable way to reproduce this annoy= ing problem. Here is a broken version of the patch suggested in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195097 that causes (I t= hink!) similar panic. I have fed rm_free_unused_clients null pointer only on one occasion and it crashed where I expected it to crash -- on exiting 3D progr= ams. In that bug they suggest that "Here rm_free_unused_clients is called with a null pointer. This function is not open source, but from the panic my guess= is it's not happy being called with a null pointer.", which pretty much may be= the case here. STEPS TO REPRODUCE A 1. Install driver with patch applied. 2. Start a 3D program (I used Blender). 3. Exit the program. STEPS TO REPRODUCE B 1. Start X. 2. Kill X. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205903-6-xn17doHEnH>