Bug 84862

Summary: [BYT] igt/kms_flip_tiling/flip-changes-tiling sporadically fails
Product: DRI Reporter: Guo Jinxian <jinxianx.guo>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: high CC: christophe.prigent, intel-gfx-bugs
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: HSW i915 features: display/Other
Attachments:
Description Flags
dmesg none

Description Guo Jinxian 2014-10-10 08:27:05 UTC
Created attachment 107651 [details]
dmesg

==System Environment==
--------------------------
Regression: Yes. 
It's a igt regression issue
Good commit:764772c3c8059a6a9d1a569d9c4bd180e11c4d33
Bad commit:b7d80d104758fb4c90723246aed943c0097c6156

Non-working platforms: BYT

==kernel==
--------------------------
origin/drm-intel-nightly: ea4bec8e96ea8b33b49a7892c1c7f20041a56da6(fails)
    drm-intel-nightly: 2014y-10m-09d-07h-58m-45s UTC integration manifest
origin/drm-intel-next-queued: a128efeaa64609a9672b51bb37bb703e1b0f0128(fails)
    drm/i915: Suppress no action noise from oom shrinker
origin/drm-intel-fixes: bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9(fails)
    Linux 3.17

==Bug detailed description==
igt/kms_flip_tiling/flip-changes-tiling fails

Output:
root@x-byt06:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_flip_tiling --run-subtest flip-changes-tiling
IGT-Version: 1.8-g7f82289 (x86_64) (Linux: 3.17.0_drm-intel-nightly_ea4bec_20141010+ x86_64)
Test assertion failure function test_flip_changes_tiling, file kms_flip_tiling.c:110:
Failed assertion: igt_crc_equal(&reference_crc, &crc)
Subtest flip-changes-tiling: FAIL (1.364s)


==Reproduce steps==
---------------------------- 
1. ./kms_flip_tiling --run-subtest flip-changes-tiling
Comment 1 Guo Jinxian 2014-11-06 08:10:54 UTC
af79fce66d023b300f308ec78289c616c81037d3 is the first bad commit
Author:     Damien Lespiau <damien.lespiau@intel.com>
AuthorDate: Mon Oct 6 18:23:33 2014 +0100
Commit:     Damien Lespiau <damien.lespiau@intel.com>
CommitDate: Mon Oct 6 18:52:06 2014 +0100


    overlay: Fix compilation warning when not having xrandr

    Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>

:040000 040000 5a03db3015dd502aff621f5dc3369e571d71cfb1 0ae9bcbcdb508e21848ef8f8bdbce313de04450d M      overlay
Comment 2 Chris Wilson 2014-11-06 08:27:00 UTC
That's an incorrect bisect.
Comment 3 Guo Jinxian 2014-11-06 09:29:54 UTC
(In reply to Chris Wilson from comment #2)
> That's an incorrect bisect.

Sorry, I checked it again, it's an unstable issue.
Comment 4 lu hua 2014-12-30 01:49:14 UTC
Test on latest -nightly kernel, it sporadically fails. 
root@x-bytm02:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_flip_tiling --run-subtest flip-changes-tiling
IGT-Version: 1.9-geb799b2 (x86_64) (Linux: 3.18.0_drm-intel-nightly_4fa231_20141229+ x86_64)
Test assertion failure function test_flip_changes_tiling, file kms_flip_tiling.c:113:
Failed assertion: igt_crc_equal(&reference_crc, &crc)
Subtest flip-changes-tiling: FAIL (0.244s)
Comment 5 Humberto Israel Perez Rodriguez 2015-09-23 15:59:30 UTC
also this two cases failing on SKL-Y with the following kernel :

Kernel commit log:
commit b4c4542ba1abfb0d3d6913504502573bf2c62b12
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Aug 28 15:51:30 2015 +0200
drm-intel-nightly: 2015y-08m-28d-13h-50m-34s UTC integration manifest

subtest	- kms_flip_tiling@flip-changes-tiling-y
subtest	- kms_flip_tiling@flip-changes-tiling-yf
Comment 6 Humberto Israel Perez Rodriguez 2015-10-15 16:56:15 UTC
Reproduced on HSW with the latest configuration:

Configuration :
---------------------------------------------
kernel: 4.3.0-rc4-drm-intel-testing-2015-10-10
xorg-server-1.17.2
libdrm-2.4.65
xf86-video-intel-2.99.917
mesa-11.0.2
libva-1.6.1
intel-driver-1.6.1
cairo-1.14.2
IGT Version : 1.12-g1f9e055
Comment 7 Ricardo 2017-02-22 19:28:50 UTC
the test executed are passing in SKL reviewed in ww07 results from IGT ALL

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.