Summary: | [IVB/BYT/BDW/BSW]Piglit spec_glsl-1.50_execution_texelFetchOffset_gs-texelFetch-isampler1DArray sporadically causes GPU hang | ||
---|---|---|---|
Product: | Mesa | Reporter: | lu hua <huax.lu> |
Component: | Drivers/DRI/i965 | Assignee: | Jordan Justen <jljusten> |
Status: | VERIFIED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | high | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
lu hua
2014-08-15 02:23:33 UTC
I suspect this was fixed by: commit c860a379d2fa09da1711591b6aef4a885d224ea0 Author: Jordan Justen <jordan.l.justen@intel.com> Date: Thu Jul 31 00:16:19 2014 -0700 i965/miptree: Layout 1D Array as 2D Array with height of 1 1D array miptrees were being laid out as a 2D texture with 1 slice. This happened due to the mesa core storing the 1D array slice count in the height field. On Intel hardware, we want to create a 2D array with a height of 1 for the 1D array case. Fixes assertion failure in piglit (gen6, gen8): spec/glsl-1.30/execution/tex-miplevel-selection textureOffset 1DArrayShadow In release builds of Mesa, this test was observed to cause a GPU hang on gen8. Signed-off-by: Jordan Justen <jordan.l.justen@intel.com> Cc: "10.2" <mesa-stable@lists.freedesktop.org> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=81450 Tested-by: Ben Widawsky <ben@bwidawsk.net> Reviewed-by: Chris Forbes <chrisf@ijw.co.nz> If not, please reopen. Thanks! Fixed. output: 65x1x5 PIGLIT: {"result": "pass" } dmesg: [ 2211.392755] [drm:i915_gem_open] [ 2211.429200] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 2211.429510] [drm:valleyview_set_rps] GPU freq request from 167 MHz (191) to 854 MHz (224) [ 2211.458891] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 2212.636630] [drm:valleyview_set_rps] GPU freq request from 854 MHz (224) to 167 MHz (191) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.