From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 72648] All 3 monitor EDIDs show the same Date: Fri, 13 Dec 2013 18:12:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0760044341==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id AB1ACFB495 for ; Fri, 13 Dec 2013 10:12:29 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0760044341== Content-Type: multipart/alternative; boundary="1386958349.e6D6aa0.32642"; charset="us-ascii" --1386958349.e6D6aa0.32642 Date: Fri, 13 Dec 2013 18:12:29 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=72648 --- Comment #8 from jim.cromie@gmail.com --- (In reply to comment #4) > According to your log, all the EDIDs are correct. It looks like the drm > sysfs layer incorrectly reports the same edid for connectors via sysfs, but > the driver has the correct information. yes, 3 different monitors are identified: [jimc@groucho bootlogs]$ grep Manufacturer /var/log/Xorg.0.log [ 30.170] (II) RADEON(0): Manufacturer: DEL Model: a039 Serial#: 876102485 [ 30.171] (II) RADEON(0): Manufacturer's mask: 0 [ 30.205] (II) RADEON(0): Manufacturer: ACR Model: ad99 Serial#: 1914720286 [ 30.206] (II) RADEON(0): Manufacturer's mask: 0 [ 30.269] (II) RADEON(0): Manufacturer: LNX Model: 0 Serial#: 0 [ 30.269] (II) RADEON(0): Manufacturer's mask: 0 fwiw, the last one is an AOC E2252S monitor, I guess "LNX" is a placeholder/default due to the Raw EDID errors, happening since I plugged in the AOC. [ 2.362551] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 153 [ 2.362594] Raw EDID: [ 2.362601] 00 ff ff ff ff ff ff 00 05 e3 52 22 db 06 00 00 [ 2.362623] 1b 17 01 03 68 30 1b 78 2a ee d1 a5 55 48 37 ff [ 2.362644] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 2.362666] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 2.362687] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 2.362709] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 2.362731] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 2.362752] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Those remainder errors appear to be random, varying between the 2 boots of the rc3-00174 kernel that I recorded (and the others too) [jimc@groucho bootlogs]$ grep remainder 3.13.0-rc3-x2a-00174-g9538e10-*/dmesg | sort -t: -k2 3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 119 3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130 3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 200 3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 241 3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 243 3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 244 3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 251 3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 87 So I agree that sysfs is somehow to blame for the original worry. I guess I'll post over on LKML, and refer back to this bug-rpt. After testing if the EDID cmdline addition might be involved. -- You are receiving this mail because: You are the assignee for the bug. --1386958349.e6D6aa0.32642 Date: Fri, 13 Dec 2013 18:12:29 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 8 on bug 72648 from 
(In reply to comment #4)
> According to your log, all the EDIDs are correct.  It looks like the drm
> sysfs layer incorrectly reports the same edid for connectors via sysfs, but
> the driver has the correct information.


yes, 3 different monitors are identified:

[jimc@groucho bootlogs]$ grep Manufacturer /var/log/Xorg.0.log
[    30.170] (II) RADEON(0): Manufacturer: DEL  Model: a039  Serial#: 876102485
[    30.171] (II) RADEON(0): Manufacturer's mask: 0
[    30.205] (II) RADEON(0): Manufacturer: ACR  Model: ad99  Serial#:
1914720286
[    30.206] (II) RADEON(0): Manufacturer's mask: 0
[    30.269] (II) RADEON(0): Manufacturer: LNX  Model: 0  Serial#: 0
[    30.269] (II) RADEON(0): Manufacturer's mask: 0

fwiw, the last one is an AOC E2252S monitor,
I guess "LNX" is a placeholder/default due to the Raw EDID errors, 
happening since I plugged in the AOC.

[    2.362551] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
remainder is 153
[    2.362594] Raw EDID:
[    2.362601]          00 ff ff ff ff ff ff 00 05 e3 52 22 db 06 00 00
[    2.362623]          1b 17 01 03 68 30 1b 78 2a ee d1 a5 55 48 37 ff
[    2.362644]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    2.362666]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    2.362687]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    2.362709]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    2.362731]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    2.362752]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff


Those remainder errors appear to be random, varying between the 2 boots
of the rc3-00174 kernel that I recorded (and the others too)

[jimc@groucho bootlogs]$ grep remainder 3.13.0-rc3-x2a-00174-g9538e10-*/dmesg |
sort -t: -k2
3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 119
3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 128
3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 130
3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 200
3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 241
3.13.0-rc3-x2a-00174-g9538e10-2ndboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 243
3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 244
3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 251
3.13.0-rc3-x2a-00174-g9538e10-1stboot/dmesg: [drm:drm_edid_block_valid] *ERROR*
EDID checksum is invalid, remainder is 87


So I agree that sysfs is somehow to blame for the original worry.
I guess I'll post over on LKML, and refer back to this bug-rpt.
After testing if the EDID cmdline addition might be involved.

You are receiving this mail because:
  • You are the assignee for the bug.
--1386958349.e6D6aa0.32642-- --===============0760044341== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0760044341==--