[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

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Product|DRI                         |Mesa
         QA Contact|intel-gfx-bugs at lists.freede |intel-3d-bugs at lists.freedes
                   |sktop.org                   |ktop.org
           Assignee|intel-gfx-bugs at lists.freede |intel-3d-bugs at lists.freedes
                   |sktop.org                   |ktop.org
          Component|DRM/Intel                   |Drivers/DRI/i965
            Version|DRI git                     |git

--- Comment #5 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to Mark Janes from comment #4)
> 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.

That is not what that means at all.

-- 
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/20161213/3538c20a/attachment.html>