Bug 88917 - [IVB bisected]igt/kms_cursor_crc subcase fail.
Summary: [IVB bisected]igt/kms_cursor_crc subcase fail.
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Matt Roper
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-02 09:07 UTC by Ding Heng
Modified: 2017-07-03 12:28 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg for kms_cursor_crc sub cases (61.66 KB, text/plain)
2015-02-02 09:07 UTC, Ding Heng
no flags Details

Description Ding Heng 2015-02-02 09:07:18 UTC
Created attachment 113042 [details]
dmesg for kms_cursor_crc sub cases

==System Environment==
--------------------------
Regression: yes
Non-working platforms:  IVB

==kernel==
--------------------------
drm-intel-nightly/8b4216f91c7bf8d3459cadf9480116220bd6545e(2015-02-02)


==Bug detailed description==
-----------------------------
Affected cases:
igt/kms_cursor_crc/cursor-64x64-offscreen 
igt/kms_cursor_crc/cursor-256x256-offscreen 

./kms_cursor_crc --run-subtest cursor-64x64-offscreen
IGT-Version: 1.9-g51d87b8 (x86_64) (Linux: 3.19.0-rc6_drm-intel-nightly_8b4216_20150202+ x86_64)
Test requirement not met in function run_test, file kms_cursor_crc.c:345:
Test requirement: valid_tests
no valid crtc/connector combinations found
Subtest cursor-64x64-offscreen: SKIP (0.000s)

./kms_cursor_crc --run-subtest cursor-256x256-offscreen
IGT-Version: 1.9-g51d87b8 (x86_64) (Linux: 3.19.0-rc6_drm-intel-nightly_8b4216_20150202+ x86_64)
Test requirement not met in function run_test, file kms_cursor_crc.c:345:
Test requirement: valid_tests
no valid crtc/connector combinations found
Subtest cursor-256x256-offscreen: SKIP (0.000s)

==Reproduce steps==
---------------------------- 
1. ./kms_cursor_crc --run-subtest cursor-256x256-offscreen
2. ./kms_cursor_crc --run-subtest cursor-64x64-offscreen
Comment 1 Ding Heng 2015-02-02 09:09:51 UTC
a679064a7e9e8799177a64a31668a34a1bc6a4f1 is the first bad commit.


commit a679064a7e9e8799177a64a31668a34a1bc6a4f1
Author:     Matt Roper <matthew.d.roper@intel.com>
AuthorDate: Fri Jan 30 16:22:37 2015 -0800
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Sat Jan 31 10:35:46 2015 +0100

    drm/i915: Switch planes from transitional helpers to full atomic helpers
    
    There are two sets of helper functions provided by the DRM core that can
    implement the .update_plane() and .disable_plane() hooks in terms of a
    driver's atomic entrypoints.  The transitional helpers (which we have
    been using so far) create a plane state and then use the plane's atomic
    entrypoints to perform the atomic begin/check/prepare/commit/finish
    sequence on that single plane only.  The full atomic helpers create a
    top-level atomic state (which is capable of holding multiple object
    states for planes, crtc's, and/or connectors) and then passes the
    top-level atomic state through the full "atomic modeset" pipeline.
    
    Switching from the transitional to full helpers here shouldn't result in
    any functional change, but will enable us to exercise/test more of the
    internal atomic pipeline with the legacy API's used by existing
    applications.
    
    Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Comment 2 Jani Nikula 2015-02-04 08:29:01 UTC
Please try this IGT patch http://patchwork.freedesktop.org/patch/41592
Comment 3 Ding Heng 2015-02-06 05:41:35 UTC
(In reply to Jani Nikula from comment #2)
> Please try this IGT patch http://patchwork.freedesktop.org/patch/41592

install this patch in igt commit: bef692d9f3556caf3e901de62f3b24d1aec5798e

commit bef692d9f3556caf3e901de62f3b24d1aec5798e
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Tue Feb 3 20:13:56 2015 +0100

    tests/gem_userptr_blits: Race between close and invalidate

This issue still exist.
Comment 4 Matt Roper 2015-02-13 18:09:17 UTC
Is this actually a failure?  It looks like a skip to me (which is still odd and needs to be investigated).  Does it happen every single time you run the test or just sometimes?

Would it be possible to get a dmesg log with debugging flags turned on?
Comment 5 Ding Heng 2015-02-15 06:39:55 UTC
(In reply to Matt Roper from comment #4)
> Is this actually a failure?  It looks like a skip to me (which is still odd
> and needs to be investigated).  Does it happen every single time you run the
> test or just sometimes?

Would it be possible to get a dmesg log with
> debugging flags turned on?

This issue disapear with latest IGT and kernel drm-intel-nightly_15-02-02, I guess this issue is caused by IGT. please refer to bug 89054. Change state to verified.
Comment 6 Jari Tahvanainen 2017-07-03 12:28:21 UTC
Closing old verified+fixed.


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.