Bug 79408 - [snb] frequent black screen on HDMI output with lost EDIDs
Summary: [snb] frequent black screen on HDMI output with lost EDIDs
Status: CLOSED NOTABUG
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: 2014-05-29 11:02 UTC by Mathieu
Modified: 2016-10-07 10:29 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg output filtered on drm / i915 lines (5.84 KB, text/plain)
2014-05-29 11:02 UTC, Mathieu
no flags Details
Xorg log file (215.51 KB, text/plain)
2014-05-29 11:02 UTC, Mathieu
no flags Details

Description Mathieu 2014-05-29 11:02:12 UTC
Created attachment 100101 [details]
dmesg output filtered on drm / i915 lines

Hi,

I use an HTPC setup and I'm having frequent black screen (loss of video and audio).
I don't really known where to start and what information to give. I can tell that I did not have this kind of issues a few months ago.

Can you give me advice on what logs to get, what output debug to activate ?
Comment 1 Mathieu 2014-05-29 11:02:39 UTC
Created attachment 100102 [details]
Xorg log file
Comment 2 Chris Wilson 2014-05-29 18:30:29 UTC
Your ddx is quite old, and has a couple of known bugs with TearFree - which have the symptom of a black screen. Please either upgrade or try disabling TearFree and see if that cures the problem.
Comment 3 Mathieu 2014-05-31 06:38:08 UTC
Thank you for taking time to respond.

I forgot to mention that I've installed an older ddx to see if the problem goes away. Now, i'm back with the most current version available in my distro (gentoo) :

[598382.917] (II) Module intel: vendor="X.Org Foundation"
[598382.917]    compiled for 1.15.0, module version = 2.99.911
[598382.917]    Module class: X.Org Video Driver
[598382.917]    ABI class: X.Org Video Driver, version 15.0

Also, I disabled TearFree. As a result, I now seeing tearing in the upper part of the screen, and I still got the frequent black screen :(

Is it normal to see the EDID checksum errors ?
If I take the EDID that is dumped in the Xorg log, it is okay (checksum ok, correct infos displayed). But I also see a some lines like that in the dmesg output (some = 25 times in a 7 days uptime)

[599210.198083] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 207
[599210.233511] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 203
[599210.233515] Raw EDID:
[599210.233518]         00 ff ff ff ff ff ff 00 65 a8 73 31 00 00 00 00
[599210.233520]         00 16 01 03 80 00 00 78 0a 0d c9 a0 57 47 98 27
[599210.233522]         12 48 4c 00 00 00 01 01 01 01 01 01 01 01 01 01
[599210.233523]         01 01 01 01 01 01 01 1d 80 18 71 1c 16 20 58 2c
[599210.233525]         25 00 c4 8e 21 3f 3f 40 40 ff ff 00 00 00 00 00
[599210.233526]         00 00 ff ff 3d 3d ff ff 00 00 00 00 00 00 00 00
[599210.233528]         00 00 00 00 00 00 00 0a 20 20 20 20 00 00 00 fd
[599210.233530]         00 17 79 0f 5b 0f 00 0a 20 20 20 20 20 20 01 19
[599210.329346] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 94
[604459.748941] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 180
[604459.782970] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 203
[604459.782977] Raw EDID:
[604459.782980]         00 ff ff ff ff ff ff 00 65 a8 73 31 00 00 00 00
[604459.782982]         00 16 01 03 80 00 00 78 0a 0d c9 a0 57 47 98 27
[604459.782984]         12 48 4c 00 00 00 01 01 01 01 01 01 01 01 01 01
[604459.782985]         01 01 01 01 01 01 01 1d 80 18 71 1c 16 20 58 2c
[604459.782987]         25 00 c4 8e 21 3f 3f 40 40 ff ff 00 00 00 00 00
[604459.782989]         00 00 ff ff 3d 3d ff ff 00 00 00 00 00 00 00 00
[604459.782990]         00 00 00 00 00 00 00 0a 20 20 20 20 00 00 00 fd
[604459.782992]         00 17 79 0f 5b 0f 00 0a 20 20 20 20 20 20 01 19
[615317.489681] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 158
[615317.525021] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 192
[615317.525025] Raw EDID:
[615317.525028]         00 ff ff ff ff ff ff 00 65 a8 73 31 00 00 00 00
[615317.525030]         00 16 01 03 80 00 00 78 0a 0d c9 a0 57 47 98 27
[615317.525032]         12 48 4c 00 00 00 01 01 01 01 01 01 01 01 01 01
[615317.525033]         01 01 01 01 01 01 01 1d 80 18 71 1c 16 20 58 2c
[615317.525035]         25 00 c4 8e 21 00 3f 3f 40 40 ff ff 00 00 00 00
[615317.525036]         00 00 ff ff ff 3d 3d ff ff 00 00 00 00 00 00 00
[615317.525038]         00 00 00 00 00 00 00 00 20 20 20 20 00 00 00 fd
[615317.525040]         00 17 79 0f 5b 0f 00 0a 20 20 20 20 20 20 01 19
Comment 4 Chris Wilson 2014-05-31 06:46:19 UTC
(In reply to comment #3)
> Thank you for taking time to respond.
> 
> I forgot to mention that I've installed an older ddx to see if the problem
> goes away. Now, i'm back with the most current version available in my
> distro (gentoo) :
> 
> [598382.917] (II) Module intel: vendor="X.Org Foundation"
> [598382.917]    compiled for 1.15.0, module version = 2.99.911
> [598382.917]    Module class: X.Org Video Driver
> [598382.917]    ABI class: X.Org Video Driver, version 15.0
> 
> Also, I disabled TearFree. As a result, I now seeing tearing in the upper
> part of the screen, and I still got the frequent black screen :(

That rules out a known bug as being the root cause. So onto the EDID.

> Is it normal to see the EDID checksum errors ?

It is infrequent. They do happen transiently with glitchy hardware, typically cables. (More often you have machines/monitors where the EDID are always wrong, i.e. bad firmware.)

> If I take the EDID that is dumped in the Xorg log, it is okay (checksum ok,
> correct infos displayed). But I also see a some lines like that in the dmesg
> output (some = 25 times in a 7 days uptime)

The EDID is used to check that there is a valid connection to the monitor, and the connection is checked periodically (it should only happen as a result of a hotplug event from the hardare). The EDID is re-read if corruption is detected, so it may not be fatal, but if no valid EDID is found, it will be assumed that the display is disconnected and will be turned off. If you have a static configuration, you may like to try e.g. drm_kms_helper.edid=HDMI-A-1:my.edid (and cp /sys/class/drm/card0-HDMI-A-1/edid /lib/firmware/my.edid)
Comment 5 Chris Wilson 2014-06-05 11:57:45 UTC
Any chance you can rule out a bad cable?
Comment 6 Mathieu 2014-06-05 16:59:11 UTC
Hi, as you suspected, I think it was a bad cable.

I started by testing the a provided EDID (using the drm_kms_helper trick). It worked by I saw strange things :
- the device name was replaced by '@@@' (in the XBMC screen)
- the audio capabilities reported only PCM and AC3 (and was missing AC3+, DTS, and others)

so I reverted back this change.

Then I exchanged the cable (2 days ago). Just touching the cable head was producting either black screen or graphics corruption (a lot of "colored snow").

Since I exchanged the cable, I did not see the black screen again (during 2 evenings).

Strangely, I also tested the bad cable a few minutes in another set of equipment (another TV and another device) and I didn't saw any problems, even when trying to move/bend the cable. Anyway, I'll stay in this setup.

So I guess you can change the status to resolved/notabug ?

I thank you again for your time.
Best regards !
Comment 7 Jari Tahvanainen 2016-10-07 10:29:28 UTC
Closing notabug (bad cable).


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.