Created attachment 105211 [details] dmesg ==System Environment== -------------------------- Regression: Yes. Results of nightly test(13/8) were passed. I am unable to find good commit on both kernel and IGT Non-working platforms: HSW ==kernel== -------------------------- origin/drm-intel-nightly: 257d90d13794c2eb545ab0d6c708f21e2a0378b6(fails) drm-intel-nightly: 2014y-08m-21d-10h-03m-09s integration manifest origin/drm-intel-next-queued: 3a5f87c286515c54ff5c52c3e64d0c522b7570c0(causes system hang bug 81483) drm: fix plane rotation when restoring fbdev configuration origin/drm-intel-fixes: 1a125d8a2c22b11741fc47d4ffcf7a5ffa044dd3(fails) drm/i915: don't try to retrain a DP link on an inactive CRTC ==Bug detailed description== igt/kms_cursor_crc some subcases skip Case list: igt/kms_cursor_crc/cursor-128-offscreen igt/kms_cursor_crc/cursor-128-onscreen igt/kms_cursor_crc/cursor-128-random igt/kms_cursor_crc/cursor-128-sliding igt/kms_cursor_crc/cursor-256-offscreen igt/kms_cursor_crc/cursor-256-onscreen igt/kms_cursor_crc/cursor-256-random igt/kms_cursor_crc/cursor-256-sliding igt/kms_cursor_crc/cursor-64-offscreen igt/kms_cursor_crc/cursor-64-onscreen igt/kms_cursor_crc/cursor-64-random igt/kms_cursor_crc/cursor-64-sliding igt/kms_cursor_crc/cursor-size-change Output: [root@x-hsw24 tests]# ./kms_cursor_crc --run-subtest cursor-128-offscreen IGT-Version: 1.7-g4d2f511 (x86_64) (Linux: 3.17.0-rc1_drm-intel-nightly_257d90_20140825+ x86_64) Test requirement not met in function run_test, file kms_cursor_crc.c:331: Test requirement: !(valid_tests) no valid crtc/connector combinations found Subtest cursor-128-offscreen: SKIP ==Reproduce steps== ---------------------------- 1. ./kms_cursor_crc --run-subtest cursor-128-offscreen
No connectors? Is that expected?
(In reply to comment #1) > No connectors? Is that expected? Maybe the connector was dropped. I retest on latest -nightly(51c49eafab38a20bdd12344d31d09810c9b0c3f6), the result passes.
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.