Bug 55901 - [IVB/HSW]I-G-T/testdisplay -p fails with modes 1400x1050 and 1366x768
Summary: [IVB/HSW]I-G-T/testdisplay -p fails with modes 1400x1050 and 1366x768
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Damien Lespiau
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-12 08:12 UTC by Guang Yang
Modified: 2017-10-06 14:48 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg info after running testdisplay -p (477.10 KB, text/plain)
2012-10-12 08:12 UTC, Guang Yang 		no flags Details
wrong screen shots. (450.14 KB, image/jpeg)
2012-10-12 08:16 UTC, Guang Yang 		no flags Details
right screen shots. (621.60 KB, image/jpeg)
2012-10-12 08:17 UTC, Guang Yang 		no flags Details
ILK(x-pk1) testdisplay -p dmesg of incorrect mode (123.94 KB, text/plain)
2012-10-15 07:22 UTC, shui yangwei 		no flags Details
View All

Description Guang Yang 2012-10-12 08:12:34 UTC 
Created attachment 68474 [details]
dmesg info after running testdisplay -p

System Environment:
--------------------------
Platform:   Ivybridge/Haswell
Kernel: (drm-intel-fixes)c3495ce9785764541d5922bead59da8739be3116

Bug detailed description:
-------------------------
   On IVB/HSW platform ,running I-G-T/testdisplay with command "testdisplay -p 1000,1000,0,0,1000,1000", the mode 1400x1050 and 1366x768 fail to show the correctly screen. I attach the dmesg and the screen shots.
Comment 1 Guang Yang 2012-10-12 08:16:54 UTC 
Created attachment 68475 [details]
wrong screen shots.

(In reply to comment #0)
> Created attachment 68474 [details]
> dmesg info after running testdisplay -p
> 
> System Environment:
> --------------------------
> Platform:   Ivybridge/Haswell
> Kernel: (drm-intel-fixes)c3495ce9785764541d5922bead59da8739be3116
> 
> Bug detailed description:
> -------------------------
>    On IVB/HSW platform ,running I-G-T/testdisplay with command "testdisplay
> -p 1000,1000,0,0,1000,1000", the mode 1400x1050 and 1366x768 fail to show
> the correctly screen. I attach the dmesg and the screen shots.
With DP and HDMI and VGA all have this issue.
Comment 2 Guang Yang 2012-10-12 08:17:25 UTC 
Created attachment 68476 [details]
right screen shots.
Comment 3 shui yangwei 2012-10-15 07:22:18 UTC 
Created attachment 68568 [details]
ILK(x-pk1) testdisplay -p dmesg of incorrect mode

System Environment:
--------------------------
Platform:   Piketon
Kernel: (drm-intel-testing)6760818aad5622d7f20d7f1c45d75a8165aeaf24
Some additional commit info:
Merge: 39bc66c be3cd5e
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Oct 12 12:24:12 2012 +0200

Bug detailed description:
-------------------------
ILK machine(x-pk1) also have this issue. 
running I-G-T/testdisplay with command "testdisplay -p 100,100,0,0,100,100", the mode 1400x1050 and 1366x768 fail to show the correctly screen.
Comment 4 shui yangwei 2012-10-29 07:17:27 UTC 
Kernel: (drm-intel-testing)b9960e75b5a348759c6e8c9ffb3f45e40ad702a5
Some additional commit info:
Merge: 8e740cd 1623392
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Oct 26 21:10:48 2012 +0200



Test with this kernel, SNB machine also have this problem.
Comment 5 Daniel Vetter 2012-11-27 23:15:43 UTC 
Bug in intel-gpu-tools, fixed in

commit b11887741cdcf28d962aa7957b2f8fd30b081e6b
Author: Damien Lespiau <damien.lespiau@intel.com>
Date:   Tue Nov 27 19:14:05 2012 +0000

    testdisplay: Use the fb stride when painting the color key
Comment 6 Guang Yang 2012-11-28 02:07:45 UTC 
(In reply to comment #5)
> Bug in intel-gpu-tools, fixed in
> 
> commit b11887741cdcf28d962aa7957b2f8fd30b081e6b
> Author: Damien Lespiau <damien.lespiau@intel.com>
> Date:   Tue Nov 27 19:14:05 2012 +0000
> 
>     testdisplay: Use the fb stride when painting the color key

Ok,the issue is gone now.
Comment 7 Elizabeth 2017-10-06 14:48:07 UTC 
Closing old verified.

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.