Bug 71074

Summary: [SNB] Frequent hangs playing Minecraft
Product: Mesa Reporter: Jan Alexander Steffens (heftig) <jan.steffens>
Component: Drivers/DRI/i965Assignee: Kenneth Graunke <kenneth>
Status: RESOLVED DUPLICATE QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium CC: idr
Version: 9.2   
Hardware: Other   
OS: All   
i915 platform: i915 features:
Attachments: i915_error_state

Description Jan Alexander Steffens (heftig) 2013-10-31 04:16:48 UTC
Created attachment 88390 [details]

While playing Minecraft on GNOME Shell, the GPU frequently hangs and is reset with messages like:

[drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
[drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xd537000 ctx 1) at 0xd5371c8


Thinkpad X220 Tablet (SNB), BIOS 1.37
Arch Linux x86_64

mesa 9.2.2
libdrm 2.4.47
xf86-video-intel 2.99.905-14-g64b9f57
xorg-server 1.14.3
linux 3.11.6
gnome-shell 3.10.1
Comment 1 Jan Alexander Steffens (heftig) 2013-10-31 04:17:23 UTC
Created attachment 88391 [details]
Comment 2 Jan Alexander Steffens (heftig) 2013-10-31 04:17:50 UTC
Created attachment 88392 [details]
Comment 3 Jan Alexander Steffens (heftig) 2013-10-31 04:23:06 UTC
Created attachment 88393 [details]
Comment 4 Jan Alexander Steffens (heftig) 2013-10-31 04:24:18 UTC
Created attachment 88394 [details]
Comment 5 Jan Alexander Steffens (heftig) 2013-10-31 04:24:47 UTC
Created attachment 88395 [details]
Comment 6 Kenneth Graunke 2013-10-31 05:08:48 UTC
Hello Jan,

I believe this is bug #70151, which I just fixed a few days ago.

Could you please try with Mesa master?  (You may still get an occasional hang, but it should be /much/ less frequent, and won't have "IPEHR: 0x79050005" in the i915_error_state.)

If not, the fixes ought to land in Mesa 9.2.4.

Comment 7 Jan Alexander Steffens (heftig) 2013-11-08 23:09:31 UTC
Seems to have cleared up, indeed. No hangs so far.

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

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.