Date: Thu, 07 Apr 2016 13:09:25 +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-XNojq6hCqQ@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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205903 --- Comment #6 from mcdouga9@egr.msu.edu --- This panic happens to me with nvidia-driver-349.16 every couple months on assorted computers including today. I'm not sure if I'll be able to provide kernel dumps because this only happens on workstations where I access sensitive information and also the dumps are large. In the past this panic could be easily triggered with just startx, but now it happens at random points that seem vaguely graphics related such as opening thunderbird, opening a new tab in chromium, or sometimes using virtualbox. The panics started with FreeBSD 10, never happened on 9 and I suspect something about the binary blob just doesn't match up properly with 10. Does anyone have a reliable way of triggering this panic so I could build a clean system to reproduce it? -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205903-6-XNojq6hCqQ>