Bug 112163 - [CI][BAT]igt@kms_frontbuffer_tracking@basic - fail - Stack trace: #1 ../lib/igt_debugfs.c:377 igt_check_crc_equal()
Summary: [CI][BAT]igt@kms_frontbuffer_tracking@basic - fail - Stack trace: #1 ../lib/i...
Status: RESOLVED DUPLICATE of bug 103167
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-10-29 08:58 UTC by Lakshmi
Modified: 2019-10-30 11:51 UTC (History)
1 user (show)

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


Attachments

Description Lakshmi 2019-10-29 08:58:02 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7201/fi-tgl-y/igt@kms_frontbuffer_tracking@basic.html
IGT-Version: 1.24-g4d1f6036d (x86_64) (Linux: 5.4.0-rc4-CI-CI_DRM_7201+ x86_64)
FBC last action not supported
Can't test DRRS: Not supported.
Starting subtest: basic
Stack trace:
  #0 ../lib/igt_core.c:1716 __igt_fail_assert()
  #1 ../lib/igt_debugfs.c:377 igt_check_crc_equal()
  #2 ../tests/kms_frontbuffer_tracking.c:1567 do_crc_assertions()
  #3 ../tests/kms_frontbuffer_tracking.c:1474 __do_assertions()
  #4 ../tests/kms_frontbuffer_tracking.c:3024 __real_main3273()
  #5 ../tests/kms_frontbuffer_tracking.c:3273 main()
  #6 ../csu/libc-start.c:344 __libc_start_main()
  #7 [_start+0x2a]
Subtest basic: FAIL (58.322s)
Comment 1 CI Bug Log 2019-10-29 08:59:07 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_frontbuffer_tracking@basic - fail - Stack trace: #1 ../lib/igt_debugfs.c:377 igt_check_crc_equal()
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7201/fi-tgl-y/igt@kms_frontbuffer_tracking@basic.html
Comment 2 Maarten Lankhorst 2019-10-30 11:51:24 UTC
Same issue as 103167.

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


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.