Bug 90516 - [IVB]Igt/kms_flip subtest vblank-vs-dpms-suspend fail
Summary: [IVB]Igt/kms_flip subtest vblank-vs-dpms-suspend fail
Status: CLOSED DUPLICATE of bug 83471
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-19 09:24 UTC by ye.tian
Modified: 2017-07-24 22:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg info with drm.debug=0x1e log_buf_len=16M (348.70 KB, text/plain)
2015-05-19 09:24 UTC, ye.tian
no flags Details

Description ye.tian 2015-05-19 09:24:06 UTC
Created attachment 115897 [details]
dmesg info with drm.debug=0x1e log_buf_len=16M

System Environment:       
-----------------------------------------------------
Regression:  not sure
Non-working platforms: IVB

==Kernel==
--------------------------------------------------
commit 056608cba30c118dcd3dff3cd0a4cacbdfd9ecdb
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Mon May 18 17:19:30 2015 +0200

    drm-intel-nightly: 2015y-05m-18d-15h-18m-36s UTC integration manifest

==description==
Igt/kms_flip subtest vblank-vs-dpms-suspend fail on IVB.
Subcase list:
igt@kms_flip@vblank-vs-dpms-suspend-interruptible 
igt@kms_flip@vblank-vs-suspend 
igt@kms_flip@vblank-vs-suspend-interruptible

==Output==
[root@x-ivb6 tests]# ./kms_flip --run-subtest vblank-vs-dpms-suspend
IGT-Version: 1.10-g5253af9 (x86_64) (Linux: 4.1.0-rc3_drm-intel-nightly_056608_20150519+ x86_64)
Using monotonic timestamps
Beginning vblank-vs-dpms-suspend on crtc 20, connector 30
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 0x5 0x48 148500
.rtcwake: wakeup from "mem" using /dev/rtc0 at Tue May 19 19:16:26 2015
.rtcwake: wakeup from "mem" using /dev/rtc0 at Tue May 19 19:16:58 2015
Test assertion failure function check_state, file kms_flip.c:640:
Failed assertion: timercmp(&es->last_received_ts, &es->current_ts, <)
vblank ts before the vblank was issued!
timerdiff -1s, 994391us
Stack trace:
  #0 [__igt_fail_assert+0xf1]
  #1 [check_state+0x271]
  #2 [run_test_on_crtc_set.constprop.13+0xafc]
  #3 [run_test+0x25a]
  #4 [main+0x284]
  #5 [__libc_start_main+0xf5]
  #6 [_start+0x29]
  #7 [<unknown>+0x29]
Subtest vblank-vs-dpms-suspend failed.
**** DEBUG ****
Test requirement passed: (flags & TEST_HANG) == 0 || !is_hung(drm_fd)
Test requirement passed: modes
Beginning vblank-vs-dpms-suspend on crtc 20, connector 30
igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258 [bpp=32], tiling=0x0, size=0
igt_create_fb_with_bo_size(handle=2, pitch=7680)
igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258 [bpp=32], tiling=0x0, size=0
igt_create_fb_with_bo_size(handle=3, pitch=7680)
igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258 [bpp=32], tiling=0x100000000000001, size=0
igt_create_fb_with_bo_size(handle=4, pitch=8192)
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 0x5 0x48 148500
Test requirement passed: !igt_run_in_simulation()
Test requirement passed: !igt_run_in_simulation()
Test assertion failure function check_state, file kms_flip.c:640:
Failed assertion: timercmp(&es->last_received_ts, &es->current_ts, <)
vblank ts before the vblank was issued!
timerdiff -1s, 994391us
****  END  ****
Subtest vblank-vs-dpms-suspend: FAIL (2.443s)


Reproduce steps:
----------------------------

1, ./kms_flip --run-subtest vblank-vs-dpms-suspend
Comment 1 Ander Conselvan de Oliveira 2015-05-20 06:11:00 UTC
(In reply to ye.tian from comment #0)
> Regression:  not sure

Could you check if the tests passes with kernel 4.0?
Comment 2 ye.tian 2015-05-20 08:41:31 UTC
(In reply to Ander Conselvan de Oliveira from comment #1)
> (In reply to ye.tian from comment #0)
> > Regression:  not sure
> 
> Could you check if the tests passes with kernel 4.0?

Test fails with kernel 4.0 and latest fixes kernel.
Comment 3 Chris Wilson 2015-05-20 11:55:16 UTC
4.0 is a bad choice since that has the start of atomic. So try 3.19 or 3.18 for a baseline.
Comment 4 Chris Wilson 2015-05-20 13:54:57 UTC
Apparently 3.17 is when the first atomic transition took place, so use 3.16 as a baseline.
Comment 5 ye.tian 2015-05-21 08:19:38 UTC
It fails on 3.17,3.18,3.19.  
System hang when running it with 3.16 kernel.
Comment 6 Ander Conselvan de Oliveira 2015-06-04 13:19:18 UTC

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


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.