Bug 89630 - [all regression]igt/kms_cursor_crc/cursor-128x128-offscreen fails
Summary: [all regression]igt/kms_cursor_crc/cursor-128x128-offscreen fails
Status: CLOSED DUPLICATE of bug 84269
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords: bisect_pending
Depends on:
Blocks:
 
Reported: 2015-03-18 06:21 UTC by lu hua
Modified: 2017-07-24 22:47 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (126.97 KB, text/plain)
2015-03-18 06:21 UTC, lu hua 		no flags Details
output (3.98 KB, text/plain)
2015-03-18 06:22 UTC, lu hua 		no flags Details
View All

Description lu hua 2015-03-18 06:21:42 UTC 
Created attachment 114419 [details]
dmesg

==System Environment==
--------------------------
Regression:  yes
good commit:fd2d61341bf39d1054256c07d6eddd624ebc4241(02-28)
bad commit: e0860aeed3980d1f7b564e1b5cf51ea26740542f(03-18)


no-working platforms: i965 platforms.

==kernel==
--------------------------
drm-intel-nightly/3753ea527e539d3358a6368e77cb29ecb2e71c42
commit 3753ea527e539d3358a6368e77cb29ecb2e71c42
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Tue Mar 17 22:36:04 2015 +0100

    drm-intel-nightly: 2015y-03m-17d-21h-35m-20s UTC integration manifest

==Bug detailed description==
-----------------------------
It fails on i965 platforms.

==Reproduce steps==
---------------------------- 
1. ./kms_cursor_crc --run-subtest cursor-128x128-offscreen
Comment 1 lu hua 2015-03-18 06:22:21 UTC 
Created attachment 114420 [details]
output

Following cases also fail:
igt/kms_cursor_crc/cursor-256x256-offscreen
igt/kms_cursor_crc/cursor-64x64-offscreen
Comment 2 Jesse Barnes 2015-04-02 20:38:18 UTC 
Another dupe of the range handling issue:
error: 0 != -34

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

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.