[Bug 99048] [BYT] piglit.spec.ext_framebuffer_object.fbo-maxsize OOM disables GPU

[bugzilla-daemon at freedesktop.org]

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

Mark Janes <mark.a.janes at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[BYT]                       |[BYT]
                   |piglit.spec.ext_framebuffer |piglit.spec.ext_framebuffer
                   |_object.fbo-maxsize OOM     |_object.fbo-maxsize OOM
                   |                            |disables GPU
                 CC|                            |intel-gfx-bugs at lists.freede
                   |                            |sktop.org
            Product|Mesa                        |DRI
         QA Contact|intel-3d-bugs at lists.freedes |intel-gfx-bugs at lists.freede
                   |ktop.org                    |sktop.org
            Version|git                         |DRI git
          Component|Drivers/DRI/i965            |DRM/Intel

--- Comment #4 from Mark Janes <mark.a.janes at intel.com> ---
Assigning to the kernel team, because it appears that OOM can kill a process
while it holds a lock, generating an unrecoverable error.

To reproduce:

 1) use a device with 1GB RAM
 2) use Mesa after e9133dd9, when texture sizes were increased
 3) use piglit before 12b5938, when Ken reduced the memory footprint of
fbo-maxsize

You should see dmesg errors:
  "Unable to purge GPU memory due lock contention"

Subsequently, other GPU workloads will fail intermittently.

-- 
You are receiving this mail because:
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/20161212/76c5b3ea/attachment.html>