Bug 66778 - [gm45 regression] xf86-video-intel-2.21.11 HDMI problems
Summary: [gm45 regression] xf86-video-intel-2.21.11 HDMI problems
Status: CLOSED DUPLICATE of bug 66563
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-10 14:35 UTC by Felix
Modified: 2017-07-24 22:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
xorg.log (27.94 KB, text/plain)
2013-07-10 14:35 UTC, Felix 		no flags Details
xorg.log from xf86-video-intel-2.21.11 (24.03 KB, text/plain)
2013-07-10 18:01 UTC, Felix 		no flags Details
dmesg driver version 2.21.10 (219.98 KB, text/plain)
2013-07-11 08:29 UTC, Felix 		no flags Details
dmesg driver version 2.21.11 (184.21 KB, text/plain)
2013-07-11 08:30 UTC, Felix 		no flags Details
photo of the corrupted output (2.80 MB, image/jpeg)
2013-07-11 08:31 UTC, Felix 		no flags Details
View All

Description Felix 2013-07-10 14:35:41 UTC 
Created attachment 82278 [details]
xorg.log

Hi,

I just noticed a bug in the xf86-video-intel-2.21.11 drivers. With my Intel GMA 4500 MHD graphics chip, the HDMI output signal is corrupt: only the red color is displayed, the green and blue pixels remain dark. The issue is solved by downgrading to version 2.21.10-r1.

kernel: 3.9.6
os: Gentoo linux


x-org.conf:


Section "Monitor"
    Identifier "LVDS0"
    Option "DPMS" "false"
EndSection

Section "ServerLayout"
    Identifier "ServerLayout0"
    Option "BlankTime"  "0"
    Option "StandbyTime" "0"
    Option "SuspendTime" "0"
    Option "OffTime" "0"
EndSection
Comment 1 Chris Wilson 2013-07-10 16:13:45 UTC 
The logfile from 2.21.11 is important as well, and please double check with master.
Comment 2 Felix 2013-07-10 18:01:48 UTC 
Created attachment 82291 [details]
xorg.log from xf86-video-intel-2.21.11

Of course, please find it attached.
Comment 3 Chris Wilson 2013-07-10 18:07:03 UTC 
Ok, that looks reasonably sane. Can you please boot with drm.debug=6 and attach dmesg for both 2.21.10 and 2.21.11?
Comment 4 Felix 2013-07-11 08:29:19 UTC 
Created attachment 82322 [details]
dmesg driver version 2.21.10
Comment 5 Felix 2013-07-11 08:30:00 UTC 
Created attachment 82323 [details]
dmesg driver version 2.21.11
Comment 6 Felix 2013-07-11 08:31:27 UTC 
Created attachment 82324 [details]
photo of the corrupted output
Comment 7 Chris Wilson 2013-07-11 09:09:43 UTC 
And the actual modesetting sequence looks identical in the two dmesg. Curious. The next step is to grab intel_reg_dumper (from http://cgit.freedesktop.org/xorg/app/intel-gpu-tools) and attach the output for 2.21.10 and 2.21.11.
Comment 8 Daniel Vetter 2013-07-11 09:29:45 UTC 
Fun one ... can you please try to bisect what exact change in the ddx cause this regression?
Comment 9 Chris Wilson 2013-07-11 10:11:38 UTC 
Actually, I know what this is now. Thinking cap clearly not on, as this is

commit ebf4517a0bb510e406795c169aa21b7cc615ed31
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Jul 3 22:44:46 2013 +0100

    sna: Always read back the gamma, even for a inactive CRTC

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

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.