From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27708] [KMS] Repeated EDID errors despite everything working
Date: Sat, 1 Jan 2011 05:03:10 -0800 (PST) [thread overview]
Message-ID: <20110101130311.0698613004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27708-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=27708
--- Comment #5 from Sergej Pupykin <ps@lx-ltd.ru> 2011-01-01 05:03:10 PST ---
I have the same issue:
Acer G225HQbd at 1920x1080:
Jan 1 01:23:12 home kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum
is invalid, remainder is 130
Jan 1 01:23:12 home kernel: [drm:drm_edid_block_valid] *ERROR* Raw EDID:
Jan 1 01:23:12 home kernel: <3>00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel:
Jan 1 01:23:12 home kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum
is invalid, remainder is 217
Jan 1 01:23:12 home kernel: [drm:drm_edid_block_valid] *ERROR* Raw EDID:
Jan 1 01:23:12 home kernel: <3>00 ff ff ff ff ff ff 00 04 72 17 00 7e 1f 30 03
.........r..~.0.
Jan 1 01:23:12 home kernel: <3>21 14 01 03 68 30 1b 78 2e c5 85 a4 59 49 9a 24
!...h0.x....YI.$
Jan 1 01:23:12 home kernel: <3>12 50 54 bf ef 80 81 c0 81 40 71 4f 81 80 81 00
.PT......@qO....
Jan 1 01:23:12 home kernel: <3>01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
.......:..q8-@X,
Jan 1 01:23:12 home kernel: <3>45 00 dc 0c 11 00 01 ff ff ff ff ff ff ff ff ff
E...............
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
Jan 1 01:23:12 home kernel:
Jan 1 01:23:12 home kernel: radeon 0000:01:00.0: DVI-I-1: EDID block 0
invalid.
Jan 1 01:23:12 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Iliama ProLite E430S at 1280x1024:
Nov 28 10:43:46 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 10:58:04 home kernel: i2c i2c-0: readbytes: ack/nak timeout
Nov 28 10:58:04 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 11:48:00 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 11:52:12 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 12:08:21 home kernel: i2c i2c-0: readbytes: ack/nak timeout
Nov 28 12:08:21 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 12:33:54 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 13:05:31 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 13:16:47 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 13:21:30 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 13:26:52 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 14:43:34 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 14:50:18 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Nov 28 15:08:58 home kernel: [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a
monitor but no|invalid EDID
Both monitors were connected through DVI->VGA connector.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-01-01 13:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 22:16 [Bug 27708] New: [KMS] Repeated EDID errors despite everything working bugzilla-daemon
2010-04-16 22:16 ` [Bug 27708] " bugzilla-daemon
2010-04-16 22:16 ` bugzilla-daemon
2010-04-16 22:17 ` bugzilla-daemon
2010-04-16 22:18 ` bugzilla-daemon
2010-04-16 22:22 ` bugzilla-daemon
2011-01-01 13:03 ` bugzilla-daemon [this message]
2011-01-01 13:07 ` bugzilla-daemon
2011-01-04 23:04 ` bugzilla-daemon
2011-01-05 23:52 ` bugzilla-daemon
2011-01-12 20:57 ` bugzilla-daemon
2011-01-25 16:59 ` bugzilla-daemon
2011-01-25 17:33 ` bugzilla-daemon
2011-02-18 18:28 ` bugzilla-daemon
2011-02-18 18:41 ` bugzilla-daemon
2011-02-18 18:44 ` bugzilla-daemon
2011-02-18 19:05 ` bugzilla-daemon
2011-02-18 21:32 ` bugzilla-daemon
2012-10-23 21:40 ` bugzilla-daemon
2012-10-24 16:34 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110101130311.0698613004E@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).