Date: Fri, 08 Jan 2016 14:47:32 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194766] [drm:pid12:i915_hangcheck_elapsed] [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung Message-ID: <bug-194766-8-Y7p65fPbr3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194766-8@https.bugs.freebsd.org/bugzilla/> References: <bug-194766-8@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=3D194766 --- Comment #39 from Kenneth Salerno <kennethsalerno@yahoo.com> --- First of all, this bug has been open 14 months. I would like to believe the= re are fbsd developers left out there that care about laptop/desktop issues, a= nd so I wait. I upgraded to 10.2-RELEASE multiple times to try each "fix" and = then downgraded back to 10.1-RELEASE to have a working Xv acceleration again, bu= t at this point I will wait until I see a code fix enter the 10.2-RELEASE branch rather than try any more "workarounds" (and a clue for other users, it is in the drm2 driver not drm), or wait and see if 10.3-RELEASE incorporates chan= ges from 11-CURRENT that fix the i915kms/drm2 code. This bug is the result of the import of Linux kernel modeset driver code th= at brought the bug along with the version that was copied. If you search throu= gh Linux kernel bug reports you'll see they had the same issue, and freebsd svn logs confirm the wholesale import. Looking through the latest 11-CURRENT branch, I see some attempts in the code to stop the GPU hung messages from appearing but personally have not tested if that is a cosmetic bandaid or n= ot. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194766-8-Y7p65fPbr3>