Created attachment 99110 [details] cat /sys/class/drm/card0/error > error.txt +++ Split separate issue out of Bug #77207. Actual reporter is Benjamin Baumgärtner <bb@knacknuss.de> +++ I upgraded my Ubuntu trusty to today's state of the xorg-edgers PPA: xserver-xorg-core 2:1.15.1-0ubuntu2 xserver-xorg-video-intel 2:2.99.911+git20140507.18416b51-0ubuntu0ricotz~trusty libegl1-mesa:amd64 10.3.0~git20140514.8a9f5ecd-0ubuntu0sarvatt~trusty libgl1-mesa-dri:amd64 10.3.0~git20140514.8a9f5ecd-0ubuntu0sarvatt~trusty $ glxinfo | grep Mesa client glx vendor string: Mesa Project and SGI OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.0-devel OpenGL version string: 3.0 Mesa 10.3.0-devel I'm still experiencing problems. Garbage screen output disappeared, but the screen is stuck for 5-20 secs every 1-3 minutes. The kernel ring buffer says: [ 333.738942] [drm] stuck on render ring [ 333.738951] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 333.738952] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 333.738953] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 333.738954] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 333.738955] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 339.736311] [drm] stuck on render ring [ 339.736354] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned! [ 348.720483] [drm] stuck on render ring [ 354.729941] [drm] stuck on render ring [ 360.727429] [drm] stuck on render ring [ 360.727558] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned! [ 439.102608] init: tty1 main process ended, respawning [ 468.674648] [drm] stuck on render ring [ 647.707294] [drm] stuck on render ring [ 716.739191] [drm] stuck on render ring So I'm still having trouble, even with xserver 1.15.1 and a recent mesa version. Regards, Benjamin
Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. If you can reproduce, please capture and upload an apitrace (https://github.com/apitrace/apitrace) so that we can easily reproduce as well. I don't actually see in the report what the user did to trigger the hang.
I don't have the affected hardware in use anymore (bug report is 2+ years old!), hence I can neither test nor reproduce the issue with a recent version.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.