[Bug 110998] New: [gen9] Hang recovery fails for atomic+textureBuffer hang

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jun 25 18:50:35 UTC 2019


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

            Bug ID: 110998
           Summary: [gen9] Hang recovery fails for atomic+textureBuffer
                    hang
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: jason at jlekstrand.net
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

In https://bugs.freedesktop.org/show_bug.cgi?id=110228 we have a reported bug
where the GPU hangs in certain L3$ atomic + textureBuffer cases.  The fact that
it's hanging is most likely a userspace mesa bug.  However, I have never seen a
system come back from this hang on any kernel I've tried it on in the last two
years.  (The bug has only been open for 6 months but I've experienced the exact
same hang as far back as two years ago.)  The fact that it's hard-hanging is
definitely a kernel bug.

Steps to reproduce:

 1. Install any version of the Linux Vulkan driver (we've had this hang since
about forever so a moderately recent distro driver should work.)
 2. Download reproducer_v2 from #110228
 3. Build with cmake
 4. Run ./cs_hang 512
 5. Watch it burn

This hang is present on at least SKL, KBL, and CFL but probably also APL.  It
is not present on BDW or ICL so it can't be tested there (though the recovery
path might still have a bug on those platforms).

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


More information about the intel-gfx-bugs mailing list