Bug 61041 - [Pineview]I-G-T/testdisplay && VGA 1600x1200 65Hz messing the screen
Summary: [Pineview]I-G-T/testdisplay && VGA 1600x1200 65Hz messing the screen
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg 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: 2013-02-18 07:55 UTC by yanbing
Modified: 2017-07-24 22:58 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments
mess-screen.dmesg (88.06 KB, text/plain)
2013-02-18 07:55 UTC, yanbing 		no flags Details
screen mess(VGA-1600x1200-65Hz) .jpg (1.54 MB, image/jpeg)
2013-02-18 07:57 UTC, yanbing 		no flags Details
Don't try to be smart about reg access (717 bytes, patch)
2013-02-19 06:09 UTC, Ben Widawsky 		no flags Details | Splinter Review
reg_dumper.log (12.22 KB, text/plain)
2013-02-19 06:30 UTC, yanbing 		no flags Details
View All

Description yanbing 2013-02-18 07:55:25 UTC 
Created attachment 75032 [details]
mess-screen.dmesg

Environment:
--------------------------
Kernel: (drm-intel-next-queued)1ca6bae2b153e5037a05685fb89852bcc9556afe
Some additional commit info:
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Jan 18 19:11:38 2013 +0200

    drm/i915: Implement pipe CSC based limited range RGB output

Steps:
---------------------------

./testdisplay -o (the specific mode like below)

CRTS(3):[0]  1600x1200 65 1600 1664 1856 2160 1200 1201 1204 1250 0x5 0x40 175500


Result:
--------------------------
1.The screen is messing.
2.Just on pineview platform,other platforms normal.
3.The model of the monitor: HP 2309p , but other ones we had just don't contain this mode.
4.I attached the photo and dmesg.
Comment 1 yanbing 2013-02-18 07:57:35 UTC 
Created attachment 75033 [details]
screen mess(VGA-1600x1200-65Hz) .jpg
Comment 2 Daniel Vetter 2013-02-18 10:01:12 UTC 
Offhand I don't have any good idea what's going on here. I guess this is a regression?

If so, please attach the output of intel_reg_dumper from both a working and a broken kernel. Also please try to bisect this issue.
Comment 3 yanbing 2013-02-19 02:26:23 UTC 
(In reply to comment #2)
> Offhand I don't have any good idea what's going on here. I guess this is a
> regression?
> 
> If so, please attach the output of intel_reg_dumper from both a working and
> a broken kernel. Also please try to bisect this issue.

I'm afraid to say it's not a regression. I can't find any a good point,so I can't bisect this issue.
Comment 4 yanbing 2013-02-19 05:58:08 UTC 
1.I had try this on the other monitor:Dell U3011, the issue is also exist.

2.I had try using the intel_reg_dumper,but the output is below: 

Gen2/3 Ranges are not supported. Please use unsafe access.Aborted (core dumped)

So what is mean?
Comment 5 Ben Widawsky 2013-02-19 06:09:06 UTC 
Created attachment 75089 [details] [review]
Don't try to be smart about reg access

Please try this patch and run reg_dumper again
Comment 6 yanbing 2013-02-19 06:30:22 UTC 
(In reply to comment #5)
> Created attachment 75089 [details] [review] [review]
> Don't try to be smart about reg access
> 
> Please try this patch and run reg_dumper again

Thanks for this patch,so I attached the reg_dumper.log.
Comment 7 yanbing 2013-02-19 06:30:58 UTC 
Created attachment 75090 [details]
reg_dumper.log
Comment 8 Daniel Vetter 2013-11-18 17:46:46 UTC 
Presuming fixed on latest kernel versions, please reopen if this is still broken. Thanks.

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.