*** Bug 99036 has been marked as a duplicate of this bug. ***

Quite likely to be caused by:

e9133dd90ec498cfb6a23fa22504e06488352c51
Author:     Jordan Justen <jordan.l.justen@intel.com>
CommitDate: Wed Dec 7 09:00:49 2016 -0800

i965: Increase max texture to 16k for gen7+

reducing the memory requirements allows the test to complete:

https://lists.freedesktop.org/archives/piglit/2016-December/021581.html

However, the lack of error recovery seems like a kernel bug.  After this test is killed, subsequent GPU operations fail until reboot.  Without reboot, the system will eventually hard-hang.

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.

(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.

Updating title to reflect that this issue is not platform dependent.

(In reply to Chris Wilson from comment #5)
> That is not what that means at all.

I can't even tell what you're responding to.

We're not mind readers. Why don't you tell us what you're thinking?

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1553.