[Bug 111936] New: [ICL] GPU hangs in TerrainFlyTess with Iris

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 111936
           Summary: [ICL] GPU hangs in TerrainFlyTess with Iris
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: not set
          Priority: not set
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: eero.t.tamminen at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 145683
  --> https://bugs.freedesktop.org/attachment.cgi?id=145683&action=edit
TerrainFlyTess ICL error state

Setup:
* HW: ICL-U D1
* OS: Ubuntu 18.04 with Unity desktop (compiz)
* SW: git versions of drm-tip 5.4-rc2 kernel, X server & Mesa
* Desktop uses i965, benchmarks use Iris

Use-case:
* Run SynMark TerrainFlyTess with Iris:
  MESA_LOADER_DRIVER_OVERRIDE=iris ./synmark2 OglTerrainFlyTess

Expected outcome:
* Like on GEN9, no GPU hangs

Actual outcome:
* Recoverable GPU hangs, see attachment
* Reproducibility: always

Notes:
* This test-case tests CPU<->GPU synchronization, by generating the terrain
data on-fly in 4 CPU threads with AVX, for GPU tessellation & rendering
* No idea whether these hangs are an regression. It seems to have happened
already >2 weeks ago on drm-tip v5.3 when I first did ICL testing


Kenneth from Mesa team already looked at the error state and commented that:

"This error state makes no sense, ACTHD points at the very start of the batch
and IPEHR is 0x18800101 which never appears in the error dump at all. Sounds
like a kernel bug to me."

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