Bug 92625 - [BYT SKL] piglit glx_arb_sync_control@timing subtests fail
Summary: [BYT SKL] piglit glx_arb_sync_control@timing subtests fail
Status: RESOLVED DUPLICATE of bug 92070
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Jairo Miramontes
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-23 01:27 UTC by Jairo Miramontes
Modified: 2015-10-28 14:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Dmesg.log (63.03 KB, text/plain)
2015-10-23 01:27 UTC, Jairo Miramontes
Details

Description Jairo Miramontes 2015-10-23 01:27:39 UTC
Created attachment 119123 [details]
Dmesg.log

The following Subtests of the glx_arb_sync_control@timing test case are failing on the below configuration.

<%glx@glx_arb_sync_control@timing -divisor 1
glx@glx_arb_sync_control@timing -divisor 2
glx@glx_arb_sync_control@timing -fullscreen -divisor 1
glx@glx_arb_sync_control@timing -msc-delta 1
glx@glx_arb_sync_control@timing -msc-delta 2
glx@glx_arb_sync_control@timing -waitformsc -divisor 1
glx@glx_arb_sync_control@timing -waitformsc -msc-delta 1%>


==Hardware configuration==
--------------------------------------------------

-- Platform: --
Processor: Intel(R) Celeron(R) CPU  N2820  @ 2.13GHz
Model: Toshiba Satellite C55t
Memory : 4GB

-- Software --
Linux distribution: Ubuntu 14.04.03 LTS 64Bits
BIOS: 1.10


==Test Environment==
--------------------------------------------------
kernel: 4.3.0-rc5-drm-intel-nightly
xorg-server-1.17.2
libdrm-2.4.65
xf86-video-intel-2.99.917
mesa-11.1.0-devel (git 6f39546)
libva-1.6.1
intel-driver-1.6.1
cairo-1.14.2

Additional information :
​dmesg output (option "drm.debug=0x06")
Comment 1 Emil Velikov 2015-10-23 10:30:13 UTC
Not sure if you get the memo from the earlier QA team that most/all of these tests produce inconsistent results. Or perhaps it's just my (SNB) system that behaves in such a way ?

Note: that despite being a GLX test, these results are hardware specific.
Comment 2 Chris Wilson 2015-10-23 10:34:06 UTC
The inconsistency is simply whether the display is off. The default is not to fake vblanks when all the CRTC are off, which confuses the piglit and it reports a fail rather than it cannot run a test.
Comment 3 cprigent 2015-10-23 14:11:50 UTC
Following tests are fail on SKL-Y.
glx@glx_arb_sync_control@timing -divisor 1
glx@glx_arb_sync_control@timing -divisor 2
glx@glx_arb_sync_control@timing -fullscreen -msc-delta 1
glx@glx_arb_sync_control@timing -fullscreen -msc-delta 2

Result was Pass with Mesa 11.0.3

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
BIOS : SKLSE2R1.R00.X097.B02.1509020030
ME FW : 11.0.0.1173
Ksc (EC FW): 1.19
Linux distribution: Ubuntu 14.04 LTS 64 bits
kernel 4.3.0-rc5-drm-intel-nightly+ (f14b17b) from git://anongit.freedesktop.org/drm-intel
commit f14b17b8639fb680c672d3d2f8d6414fcf0f82c4
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Oct 16 19:27:49 2015 +0200
drm-intel-nightly: 2015y-10m-16d-17h-27m-10s UTC integration manifest
Mesa master commit 6f3954618b0fe273af76af79ce9ec56566b79b2a 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
Comment 4 Ben Widawsky 2015-10-28 14:48:20 UTC

*** This bug has been marked as a duplicate of bug 92070 ***


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.