[Bug 111384] [BXT/Iris] GPU hang in SynMark compute CSCloth

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Aug 12 14:24:59 UTC 2019


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

            Bug ID: 111384
           Summary: [BXT/Iris] GPU hang in SynMark compute CSCloth
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/Iris
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: eero.t.tamminen at intel.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Created attachment 145036
  --> https://bugs.freedesktop.org/attachment.cgi?id=145036&action=edit
i915 error state for GPU hang

Setup:
- BXT J4205
- ClearLinux (30730)
- drm-tip git kernel (0330b51e91)
- Mesa git (5ed4e31c08d)
- Weston git build

Test-case:
- 3x fullscreen FullHD SynMark CSCloth compute test-case (Wayland version):
  synmark2 OglCSCloth

Actual outcome:
- Recoverable GPU hang:
-------------------------------
[ 8477.103209] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
[ 8477.103216] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 8477.103217] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 8477.103219] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 8477.103220] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 8477.103222] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 8477.104241] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 8477.105009] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed
out: {request: 00000001, RESET_CTL: 00000001}
-------------------------------

This is faster of the 2 SynMark compute tests.

I wasn't able to reproduce the hang after reboot when re-running just CSCloth
10 times, so it may depend on previous tests, or is just very hard to
reproduce.

I haven't seen such hangs with the i965 driver, and that test didn't hang on
SKL GT2 (another one did).  I didn't see such hang when running similar
test-set month ago, so it can be a regression.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20190812/69e2c32f/attachment-0001.html>


More information about the intel-3d-bugs mailing list