When the SKL kernels were upgraded, the following piglit tests regressed:
piglit.spec.ext_texture_compression_s3tc.getteximage-targets cube_array s3tc
piglit.spec.arb_texture_cube_map_array.fbo-generatemipmap-cubemap array s3tc_dxt1
Failing kernel version:
38090ed drm-intel-nightly: 2015y-09m-02d-15h-24m-23s UTC integration manifest
The passing kernel version was a drm nightly 4.1.0 kernel pulled around June 7.
Mark, why did you assign this to Ian if the kernel update made the failure happen?
Ian gets bugs by default. If I know who to assign a bug to, then I assign it directly. Who are the candidates to get this bug?
On Fri, Oct 23, 2015 at 04:34:04PM +0000, firstname.lastname@example.org wrote:
> --- Comment #2 from Mark Janes <email@example.com> ---
> Ian gets bugs by default. If I know who to assign a bug to, then I assign it
> directly. Who are the candidates to get this bug?
Kernel bugs should be assigned to Intel GFX Bugs mailing list by default.
(In reply to Mark Janes from comment #0)
> When the SKL kernels were upgraded, the following piglit tests regressed:
> piglit.spec.ext_texture_compression_s3tc.getteximage-targets cube_array s3tc
> piglit.spec.arb_texture_cube_map_array.fbo-generatemipmap-cubemap array
> Failing kernel version:
> 38090ed drm-intel-nightly: 2015y-09m-02d-15h-24m-23s UTC integration manifest
> The passing kernel version was a drm nightly 4.1.0 kernel pulled around June
Was mesa updated as well? Neil has pointed out that some of the ASTC patches may have caused these regressions.
When I wrote this bug up, I was upgrading SKL kernels and attributed the failure to that change. However, now that I am testing SKL on a regular basis, I can see that these tests regressed in Mesa since 11.0.
I bisected the test, and found that it regressed when ASTC was enabled for SKL:
Author: Nanley Chery <firstname.lastname@example.org>
AuthorDate: Tue May 19 12:28:20 2015 -0700
Commit: Nanley Chery <email@example.com>
CommitDate: Mon Aug 31 17:29:36 2015 -0700
i965: advertise ASTC support for Skylake
v2: remove OES ASTC extension reference.
Reviewed-by: Anuj Phogat <firstname.lastname@example.org>
Signed-off-by: Nanley Chery <email@example.com>
I've submitted a patch to the mailing list which fixes this issue:
I assume this bug is now fixed because these tests are passing and Nanley's patch has been merged: