[Bug 91730] New: GPU HANG: ecode 7:0:0x85fffff8, reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91730

            Bug ID: 91730
           Summary: GPU HANG: ecode 7:0:0x85fffff8, reason: Ring hung,
                    action: reset
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: screwtape at froup.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 117869
  --> https://bugs.freedesktop.org/attachment.cgi?id=117869&action=edit
Contents of /sys/class/drm/card0/error as requested

I wish I had some easy way to reproduce this with some widely-available
software, but I'm not sure what would count.

The setup:

- I'm trying to play The Witcher Enhanced Edition
- Running under Wine 1.7.49
- Mesa 10.6.3
- Xorg 2.99.917
- Linux 4.1.0
- Debian Testing
- Intel Ivy Bridge i5-3570K CPU, with HD4000 graphics

Steps to reproduce (on my machine):

- Start the game
- Load my usual saved game
- Sometimes, once the initial loading screen's progress bar gets to the 99%
mark, the hard-drive light stops flickering and the progress will pause for 10
seconds or so and then crash to desktop
- Sometimes the game loads properly, but later I'll be moving from one zone to
another and *that* loading screen will pause and crash.
- Generally, I can't play the game for more than 5-10 minutes before a crash
occurs.
- This same problem also occurs with another game called Path of Exile, in a
similar fashion: every loading screen has some percentage chance to pause and
crash.

Effects:
- When I start the game from a terminal, after a crash it displays the
following message:

    intel_do_flush_locked failed: Input/output error

- /var/log/messages receives this message:

[  807.367059] [drm] stuck on render ring
[  807.367363] [drm] GPU HANG: ecode 7:0:0x85fffff8, in witcher.EXE [4865],
reason: Ring hung, action: reset
[  807.367364] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[  807.367364] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[  807.367365] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[  807.367365] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[  807.367366] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  807.369412] drm/i915: Resetting chip after gpu hang
[  813.363894] [drm] stuck on render ring
[  813.364243] [drm] GPU HANG: ecode 7:0:0x85ffbff8, in witcher.EXE [4865],
reason: Ring hung, action: reset
[  813.366337] drm/i915: Resetting chip after gpu hang

- If I restart the game and try again, it'll crash again (usually faster), and
after a few iterations eventually the console stops responding to anything but
the Alt-SysRq keys (although I can SSH in from another computer and everything
seems to be running fine) and I have to reboot.

Because I'm using Debian Testing, it's a bit difficult to say when this
started. My recollection is that everything worked fine under Mesa 10.4, but
these errors started appearing after Debian upgraded to Mesa 10.5. Of course,
Debian was changing all kinds of stuff around that time, so it might have been
anything.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150823/0e9a92c3/attachment.html>