Lots of weird stuff happening since ubuntu 14.04 :-( The dump file mentioned is empty, so I doubt you can help, but let me know if anything more I could send. kernel: [ 4585.795286] [drm] GPU crash dump saved to /sys/class/drm/card0/error kernel: [ 4585.795287] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. kernel: [ 4585.795288] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel kernel: [ 4585.795289] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. kernel: [ 4585.795290] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. kernel: [ 4598.780409] [drm] stuck on render ring kernel: [ 4604.803085] [drm] stuck on render ring kernel: [ 4610.789759] [drm] stuck on render ring kernel: [ 4610.789814] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x19ef000 ctx 1) at 0x19ef290
(In reply to comment #0) > Lots of weird stuff happening since ubuntu 14.04 :-( > > The dump file mentioned is empty, so I doubt you can help, but let me know > if anything more I could send. The file size will be 0 regardless of whether there's something in there or not. Just cp the file somewhere.
I guess maybe I'm too late, it just says "no error state collected"
Created attachment 99027 [details] Crash dump /sys/class/drm/card0/error crash dump
Similar error for me, Ubuntu 14.04: [12592.559357] [drm] stuck on render ring [12592.559362] [drm] GPU crash dump saved to /sys/class/drm/card0/error [12592.559364] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [12592.559365] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [12592.559366] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [12592.559367] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. I have attached the crash dump (previous comment). I do not know if it is related, but I see from time to time lines on the screen that look like problems with cache flushes.
(In reply to comment #4) > I do not know if it is related, but I see from time to time lines on the > screen that look like problems with cache flushes. Unrelated to the hang. That would be a bug where someone is using an incorrect MOCS value whilst rendering to the scanout buffer.
Presuming the latter dump is the same as the original bug reporter's... *** This bug has been marked as a duplicate of bug 77104 ***
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.