Bug 101765 - [IGT] Subtest flip-vs-cursor-crc-legacy: FAIL (1.002s)
Summary: [IGT] Subtest flip-vs-cursor-crc-legacy: FAIL (1.002s)
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-12 11:08 UTC by Paul Menzel
Modified: 2017-10-11 21:38 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
cd test && ./kms_cursor_legacy (Linux 4.13 merge window) (15.15 KB, text/plain)
2017-07-12 11:08 UTC, Paul Menzel 		no flags Details
cd test && ./kms_cursor_legacy (Linux 4.9.30) (15.14 KB, text/plain)
2017-07-12 11:09 UTC, Paul Menzel 		no flags Details
View All

Description Paul Menzel 2017-07-12 11:08:25 UTC 
Created attachment 132631 [details]
cd test && ./kms_cursor_legacy (Linux 4.13 merge window)

On a Lenovo X60t with Linux 4.9.30 from Debian Stretch/testing, and Linux “4.13-merge-window” the following test fails.

```
Stack trace:
  #0 [__igt_fail_assert+0x76]
  #1 [flip_vs_cursor_crc+0x3c8]
  #2 [<unknown>+0x3c8]
Subtest flip-vs-cursor-crc-legacy: FAIL (1.002s)
```
Comment 1 Paul Menzel 2017-07-12 11:09:01 UTC 
Created attachment 132632 [details]
cd test && ./kms_cursor_legacy (Linux 4.9.30)
Comment 2 Elizabeth 2017-07-18 15:41:02 UTC 
Hello,
Could you please add dmesg with drm.debug=0xe on grub?
Thank you.
Comment 3 Elizabeth 2017-08-24 17:04:35 UTC 
Hello Paul, any update?
Comment 4 Elizabeth 2017-10-11 21:37:08 UTC 
Closing due to the incomplete information. According to https://intel-gfx-ci.01.org/tree/drm-tip/igt@kms_cursor_legacy@flip-vs-cursor-legacy.html this test is no failing on CI.
Comment 5 Elizabeth 2017-10-11 21:38:35 UTC 
If problem arise again please file a new bug with HW and SW information, dmesg and/or kern.log with debug information (drm.debug=14 on grub), and output log of the test. Thank you.

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.