Bug 81083 - [SNB/IVB/HSW/BYT Bisected]igt/kms_plane some subcases timeout
Summary: [SNB/IVB/HSW/BYT Bisected]igt/kms_plane some subcases timeout
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: high normal
Assignee: Damien Lespiau
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-09 07:24 UTC by Guo Jinxian
Modified: 2017-10-06 14:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (123.72 KB, text/plain)
2014-07-09 07:24 UTC, Guo Jinxian
no flags Details

Description Guo Jinxian 2014-07-09 07:24:22 UTC
Created attachment 102464 [details]
dmesg

==System Environment==
--------------------------
Regression: Yes. 
It's a igt regression bug.
Good commit on igt: 67e29a30d5da57fb6764a23ba9f6aa31ea2c15a8
bad commit on igt: 8d60b8267e97f9b04e42912262c170c473d4f061

Non-working platforms: SNB IVB HSW BYT

==kernel==
--------------------------
origin/drm-intel-nightly: ed4d04defe2c6962efe8f4ba3587a8e69e06d2dd(fails)
    drm-intel-nightly: 2014y-07m-08d-21h-05m-49s integration manifest
origin/drm-intel-next-queued: 31685c258e0b0ad6aa486c5ec001382cf8a64212(fails)
    drm/i915/vlv: WA for Turbo and RC6 to work together.
origin/drm-intel-fixes: 72f5fd2a9815b49d0e6df063025aa55e9bc2435d(fails)
    drm/i915/vlv: T12 eDP panel timing enforcement during reboot

==Bug detailed description==
-----------------------------
igt/kms_plane some subcases timeout

Case list:
igt/kms_plane/plane-position-covered-pipe-B-plane-1
igt/kms_plane/plane-position-covered-pipe-B-plane-2
igt/kms_plane/plane-position-covered-pipe-C-plane-1
igt/kms_plane/plane-position-covered-pipe-C-plane-2
igt/kms_plane/plane-position-hole-pipe-B-plane-1
igt/kms_plane/plane-position-hole-pipe-B-plane-2
igt/kms_plane/plane-position-hole-pipe-C-plane-1
igt/kms_plane/plane-position-hole-pipe-C-plane-2

Output:
[root@x-ivb9 tests]# ./kms_plane --run-subtest plane-position-covered-pipe-C-plane-1
IGT-Version: 1.7-g8d60b82 (x86_64) (Linux: 3.15.0-rc8_drm-intel-next-queued_1267a2_20140703+ x86_64)
Testing connector VGA-1 using pipe C plane 1
Subtest plane-position-covered-pipe-C-plane-1: TIMEOUT

==Reproduce steps==
---------------------------- 
1. ./kms_plane --run-subtest plane-position-covered-pipe-C-plane-1
Comment 1 Guo Jinxian 2014-07-10 08:42:19 UTC
de538cfc7cd649216801829daffe602f4efee08a is the first bad commit

commit de538cfc7cd649216801829daffe602f4efee08a
Author:     Damien Lespiau <damien.lespiau@intel.com>
AuthorDate: Mon Jul 7 13:30:41 2014 +0100
Commit:     Damien Lespiau <damien.lespiau@intel.com>
CommitDate: Mon Jul 7 17:59:52 2014 +0100

    kms_plane: Make the gathering of reference CRCs test agnostic
    
    We're going to add tests for panning. Both position and panning tests
    share the need to grab reference CRCs of single coloured fb, so let's
    separate this function from the position test.
    
    Cc: Lei Liu <lei.a.liu@intel.com>
    Cc: Yi Sun <yi.sun@intel.com>
    Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Comment 2 Damien Lespiau 2014-07-10 11:02:14 UTC
This should be fixed in the latest intel-gpu-tools by http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/commit/?id=c5b9615b83910f5a5c19fc84d938ea643f4e3009
Comment 3 Guo Jinxian 2014-07-15 08:53:25 UTC
Here has another issue tracked by bug 81377, close this one.

[root@x-ivb9 tests]# ./kms_plane --run-subtest plane-position-covered-pipe-C-plane-1
IGT-Version: 1.7-g3f50598 (x86_64) (Linux: 3.16.0-rc4_drm-intel-next-queued_ebcdf5_20140715+ x86_64)
Testing connector VGA-1 using pipe C plane 1
Testing connector DP-2 using pipe C plane 1
Test assertion failure function igt_wait_for_vblank, file igt_kms.c:1475:
Failed assertion: drmWaitVBlank(drm_fd, &wait_vbl) == 0
Last errno: 16, Device or resource busy
Subtest plane-position-covered-pipe-C-plane-1: FAIL
Comment 4 Elizabeth 2017-10-06 14:37:22 UTC
Closing old verified.


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.