[Bug 914184] New: kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
http://bugzilla.opensuse.org/show_bug.cgi?id=914184 Bug ID: 914184 Summary: kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: Ulrich.Windl@rz.uni-regensburg.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- It seems when the monitor is powered down (by the screensaver), it does no longer respond with a correct EDID. I see these kernel messages: kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 181 kernel: Raw EDID: kernel: 00 ff ff ff ff ff ff 00 15 c3 78 20 01 01 01 01 kernel: 0a 14 01 03 80 34 21 78 ea 1e c5 ae 4f 34 b1 26 kernel: 0e 50 54 a1 08 00 a9 40 81 80 81 40 b3 00 01 01 kernel: 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 kernel: 36 00 07 44 21 00 00 1a 00 00 00 ff 00 30 31 ff kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Another time I get this (from the same hardware): kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130 kernel: Raw EDID: kernel: 00 ff ff ff ff ff ff 00 15 c3 78 20 01 01 01 01 kernel: 0a 14 01 03 80 34 21 78 ea 1e c5 ae 4f 34 b1 26 kernel: 0e 50 54 a1 08 00 a9 40 81 80 81 40 b3 00 01 01 kernel: 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 kernel: 36 00 07 44 21 00 00 1a 00 00 00 ff 00 30 32 37 kernel: 33 34 30 32 30 0a 20 20 38 0f ff ff ff ff ff ff kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff --- # journalctl |cut -d' ' -f 5- | grep "remainder is" | sort | uniq -c 3 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130 1 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 131 1 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 160 1 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 175 3 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 181 1 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 182 1 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 24 2 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 81 Graphics is: intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600 Monitor is: Hardware Class: monitor Model: "EIZO SX2462W" Vendor: ENC "EIZO" Device: eisa 0x2078 "SX2462W" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
Ulrich Windl
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
--- Comment #3 from Ulrich Windl
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
--- Comment #4 from Ulrich Windl
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c6
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c7
--- Comment #7 from Ulrich Windl
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c8
Ulrich Windl
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c9
Ulrich Windl
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c10
Ulrich Windl
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c11
Egbert Eich
Created attachment 665326 [details] Output of "journalctl -k -b |grep drm" (compressed)
I was not able to reproduce an EDID checksum error with kernel 3.16.7-29-desktop and xorg-x11-server-7.6_1.16.1-31.1.x86_64 within a short time; However I saw the error two days ago. Maybe the system has to go to a deeper sleep to make the problem appear...
This information doesn't help us much as we don't know the version numbers of the Xserver / kernel you did observe this problem. I'm also not sure if this isn't a problem on the HW side as we have not seen EDID issues with Intel for over 2 years. I'd suggest you use a kernel/Xserver/driver & software combination which seems to have a great chance to get this problem and instead exchange all HW components after the graphics card to see if the issue persists. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c12
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c13
--- Comment #13 from Ulrich Windl
This information doesn't help us much as we don't know the version numbers of the Xserver / kernel you did observe this problem.
I wasn't aware you knew that I updated the kernel and X server since my last report. Sorry.
I'm also not sure if this isn't a problem on the HW side as we have not seen EDID issues with Intel for over 2 years. I'd suggest you use a kernel/Xserver/driver & software combination which seems to have a great chance to get this problem and instead exchange all HW components after the graphics card to see if the issue persists.
So what software do you recommend, and where do I get the hardware to replace? ;-) Maybe re-read what I've written and what you have written. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c14
--- Comment #14 from Egbert Eich
(In reply to Egbert Eich from comment #11)
This information doesn't help us much as we don't know the version numbers of the Xserver / kernel you did observe this problem.
I wasn't aware you knew that I updated the kernel and X server since my last report. Sorry.
I knew that you've update the kernel. But I cannot find anywhere where you mention the version of your previous kernel. If you are interested in getting this issue fixed you need to supply more precise information. 1. We need to know under what circumstances the condition occurs: In the original description you say: 'It seems when the monitor is powered down ...': 'It seems...' makes it pure speculation. Did you ever try to verify it? Can you verify that this happens right after waking up the monitor from standby? 2. You claimed you could not see the issue with 3.16.7-29-desktop on one day but you did on the same kernel two days before. This is at least how I read comment #8. This doesn't help us much. Was there any kernel before where this issue didn't occur? Did you really verify this? To verify this, you'd have to do 1. Currently there is too much speculation here. We don't even know if this is a regression. If there was a kernel version where it worked (and you verified that it really did - under the same circumstances as the kernel that showed the issue) we had some marker to go by.
I'm also not sure if this isn't a problem on the HW side as we have not seen EDID issues with Intel for over 2 years. I'd suggest you use a kernel/Xserver/driver & software combination which seems to have a great chance to get this problem and instead exchange all HW components after the graphics card to see if the issue persists.
So what software do you recommend, and where do I get the hardware to replace? ;-) Maybe re-read what I've written and what you have written.
Hardware to replace? How about boo#964429? This monitor looks different... I'd suggest to test a Leap 42.1 kernel on your 13.2 system. On some kernel versions the Intel driver played some games with the power wells. It is not unlikely, that the issues you are seeing are related to this as well. As long as you don't need an NVIDIA proprietary driver on this box the Leap 42.1 kernel should be just fine for you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c15
--- Comment #15 from Ulrich Windl
(...) Especially the "00 ff ff ff ff ff ff 00" pattern at the beginning of a bad EDID seems very common. That's present in valid EDIDs as well. So it seems the problem starts in the middle of an EDID message. According to http://www.boichat.ch/nicolas/ddcci/specs.html "The DDC bus is nothing else
http://bugzilla.opensuse.org/show_bug.cgi?id=914184
http://bugzilla.opensuse.org/show_bug.cgi?id=914184#c16
--- Comment #16 from Ulrich Windl
participants (1)
-
bugzilla_noreply@novell.com