Bug 112228 - [CI][RESUME] igt@kms_dp_tiled_display@basic-test-pattern - fail - Failed assertion: !(abs(usec) >= 10), Delayed page flip event from CRTC
Summary: [CI][RESUME] igt@kms_dp_tiled_display@basic-test-pattern - fail - Failed asse...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-08 08:14 UTC by Lakshmi
Modified: 2019-11-11 11:35 UTC (History)
2 users (show)

See Also:
i915 platform: TGL
i915 features: display/DP


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-11-08 08:14:09 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7266/re-tgl-u/igt@kms_dp_tiled_display@basic-test-pattern.html
Starting subtest: basic-test-pattern
(kms_dp_tiled_display:1536) CRITICAL: Test assertion failure function page_flip_handler, file ../tests/kms_dp_tiled_display.c:352:
(kms_dp_tiled_display:1536) CRITICAL: Failed assertion: !(abs(usec) >= 10)
(kms_dp_tiled_display:1536) CRITICAL: Delayed page flip event from CRTC:152 at 972:51039
Subtest basic-test-pattern failed.
Comment 1 CI Bug Log 2019-11-08 08:15:19 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_dp_tiled_display@basic-test-pattern - fail - Failed assertion: !(abs(usec) >= 10), Delayed page flip event from CRTC
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7266/re-tgl-u/igt@kms_dp_tiled_display@basic-test-pattern.html
Comment 2 Manasi 2019-11-08 17:14:55 UTC
Are there any dmesg logs on this with the 5K tiled display attached?

Manasi
Comment 3 Lakshmi 2019-11-11 11:35:24 UTC
(In reply to Manasi from comment #2)
> Are there any dmesg logs on this with the 5K tiled display attached?
> 
> Manasi

Tomi can you help here?


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.