Bug 88341

Summary: stuck on render ring
Product: DRI Reporter: r4p5w7
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
'hardinfo' report
none
Missing 'error' file
none
Fresh 'error' file. none

Description r4p5w7 2015-01-12 22:08:54 UTC 
Created attachment 112143 [details]
'hardinfo' report

Machine hangs for few seconds with following entries in dmesg:

[ 1441.820525] [drm] stuck on render ring
[ 1441.820532] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1441.820533] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1441.820533] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1441.820534] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1441.820534] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

(File '/sys/class/drm/card0/error' is empty)
Comment 1 Chris Wilson 2015-01-13 11:26:06 UTC 
/sys/class/drm/card0/error is never empty; ls lies. Please try 

$ sudo cat /sys/class/drm/card0/error | gzip > error.gz

and attach error.gz
Comment 2 r4p5w7 2015-01-13 21:54:57 UTC 
Created attachment 112182 [details]
Missing 'error' file

You are right - it wasn't really empty.
Comment 3 Chris Wilson 2015-01-13 21:58:34 UTC 
It has to be captured after the hang and before the next reboot.
Comment 4 r4p5w7 2015-01-13 22:03:07 UTC 
Oops! I'm sorry - I didn't checked it. I will post one as soon as it happens again.
Comment 5 r4p5w7 2015-01-18 18:09:52 UTC 
Created attachment 112430 [details]
Fresh 'error' file.
Comment 6 Chris Wilson 2015-01-18 19:10:26 UTC 

*** This bug has been marked as a duplicate of bug 83677 ***

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.