Setup: -------- Hardware: Platform: SKY LAKE Y A0 CPU : Intel(R) Core(TM) m5-6Y57 CPU @ 1.10GHz (family: 6, model: 78 stepping: 3) MCP : SKL-Y D1 2+2 (ou ULX-D1) QDF : QJK9 CPU : SKL D0 Chipset PCH: Sunrise Point LP C1 CRB : SKY LAKE Y LPDDR3 RVP3 CRB FAB2 Reworks : All Mandatories + FBS02,FBS03, F23, O-02 & O-06 Software Linux : Ubuntu 14.04 LTS 64 bits BIOS : SKLSE2R1.R00.X097.B02.1509020030 ME FW : 11.0.0.1173 Ksc (EC FW): 1.19 kernel 4.3.0-rc3-drm-intel-nightly+ (eb69e51) from git://anongit.freedesktop.org/drm-intel Mesa - 11.0.2 from http://cgit.freedesktop.org/mesa/mesa/ xf86-video-intel - 2.99.917 from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ Libdrm - 2.4.65 from http://cgit.freedesktop.org/mesa/drm/ Libva - 1.6.1 from http://cgit.freedesktop.org/libva/ vaapi intel-driver - 1.6.1 from http://cgit.freedesktop.org/vaapi/intel-driver Cairo - 1.14.2 from http://cgit.freedesktop.org/cairo Xorg Xserver - 1.17.2 from http://cgit.freedesktop.org/xorg/xserver Regression: ------------ Tests were Pass with Mesa 10.6.7 Steps ------ Execute command: ./piglit -s -c run deqp_gles3 results/deqp_gles3 Actual result: -------------- Following tests are fail deqp-gles3@functional@shaders@arrays@constructor@bool3_fragment deqp-gles3@functional@shaders@arrays@constructor@bool4_vertex deqp-gles3@functional@shaders@arrays@constructor@bool_vec3_fragment deqp-gles3@functional@shaders@arrays@constructor@float_vec3_vertex deqp-gles3@functional@shaders@arrays@constructor@int3_vertex Expected result: ----------------- Tests are Pass
I am unable to reproduce this on my BDW system, so it is probably a SKL-specific problem. Since this is a regression, we need a bisect.
ping
Dear Reporter, This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested. Thank you.
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.