Bug 73316

Summary: [drm] stuck on render ring
Product: xorg Reporter: ntzrmtthihu777
Component: Driver/intelAssignee: Chris Wilson <chris>
Status: RESOLVED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium CC: ntzrmtthihu777
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description ntzrmtthihu777 2014-01-06 03:27:16 UTC
Very similar bug to #70151, but grep IPEHR /sys/class/drm/card0/error returns
  IPEHR: 0x02000004
  IPEHR: 0x00000000
running linux-ck 3.12.5-1 on a Dell Latitude-XT2 notebook/tablet
Comment 1 ntzrmtthihu777 2014-01-06 03:40:16 UTC
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)

when the render ring error occurs I experience a general graphics lockup; the screen becomes frozen, but still visable at the state it was when the lock occurred, I can move my mouse but the icon (which is an enhanced replica of the old starcraft cursor) ceases its animation.

This lockup seems to occur at random; switching virtual desktops, typing in irssi, switching tabs in firefox without any graphically intense content.
Comment 2 Kenneth Graunke 2014-01-06 03:49:38 UTC
0x02000004 is a MI_FLUSH with the INHIBIT_FLUSH_RENDER_CACHE flag set.

Mesa never emits the MI_FLUSH command on GM45, so this can't be a Mesa bug.

Both UXA and SNA emit this, however.  It appears the reporter is using SNA.
Comment 3 ntzrmtthihu777 2014-01-06 04:54:40 UTC
Indeed, SNA. I'll be testing UXA for completeness's sake.
And if this is not a mesa bug what is it? I posted under mesa because of its similarity to 70151, but if this belongs elsewhere could it be migrated?
Comment 4 ntzrmtthihu777 2014-01-06 05:42:05 UTC
Yep, seems to be a SNA-specific bug, using UXA removes the issue.

Any more info I could provide?
Comment 5 Chris Wilson 2014-01-06 09:57:28 UTC
/sys/class/drm/card0/error, Xorg.0.log
Comment 6 Chris Wilson 2014-01-07 15:01:06 UTC

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

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.