Bug 1368291

Summary:

colord failed info had been found in messages with intel Broadwell processor

Product:

Red Hat Enterprise Linux 7

Reporter:

Huaisheng <yehs1>

Component:

colord

Assignee:

Richard Hughes <rhughes>

Status:

CLOSED NOTABUG

QA Contact:

Desktop QE <desktop-qa-list>

Severity:

high

Docs Contact:

Priority:

high

Version:

7.3

CC:

fchen16, fusionneur, jkachuck, rhughes, tpelka, yehs1

Target Milestone:

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2017-01-10 20:19:29 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Bug Depends On:

Bug Blocks:

1369100

Attachments:

Description	Flags
/vat/log/messages	none
sosreport	none

Description Huaisheng 2016-08-19 02:25:36 UTC

Description of problem:

22384 Aug 15 01:38:18 localhost colord: (colord:2953): Cd-WARNING **: failed to get edid data: EDID length is too small

Version-Release number of selected component (if applicable):

colord-1.2.7-2.el7.x86_64.rpm

How reproducible:


Steps to Reproduce:
1. Full install RHEL7.3Alpha1 on X3650M5 with UEFI mode
2. Boot into OS and check /var/log/messages 

Actual results:

Found there were colord: (colord:17646): Cd-WARNING **: failed to get edid data: EDID length is too small

Expected results:

Doesn't have any warning info about colord.

Additional info:

Platform: X3650M5
CPU: Intel(R) Xeon(R) CPU E5-2690 V4@ 2.6GHz(QK8X)	
Memory: 1* 4GB 1RX8 PC4-2133P-RDP-10
HDD: 1* 2.5'' SAS		
Network card: 1*Intel Ethernet Server Adapter I350-T4 	
PSU: DELTA DPS-750AB-28 REV:S2F 750W
RAID card: ServerRAID M5210	
Boot mode: UEFI

Comment 1 Huaisheng 2016-08-19 02:33:56 UTC

Created attachment 1192018 [details]
/vat/log/messages

Comment 3 Huaisheng 2016-08-29 07:09:42 UTC

Anything updated for this issue?

Comment 4 Joseph Kachuck 2016-08-29 14:43:06 UTC

Hello Lenovo,
Please attach a sosreport from a system directly after seeing this issue.

Please confirm if this worked correctly in RHEL 7.2? 

Thank You
Joe Kachuck

Comment 5 Huaisheng 2016-08-30 04:53:08 UTC

(In reply to Joseph Kachuck from comment #4)
> Hello Lenovo,
> Please attach a sosreport from a system directly after seeing this issue.
> 
> Please confirm if this worked correctly in RHEL 7.2? 
> 
> Thank You
> Joe Kachuck

Ok, I will upload sosreport later, and haven't found this issue with RHEL7.2.

Comment 6 Huaisheng 2016-08-30 04:56:16 UTC

Created attachment 1195613 [details]
sosreport

Comment 7 Joseph Kachuck 2016-08-30 14:53:48 UTC

Hello  Huaisheng ,
I apologize just want to make sure. Did it work correctly in RHEL 7.2, or was not tested in RHEL 7.2?

Thank You
Joe Kachuck

Comment 8 Huaisheng 2016-08-31 12:59:41 UTC

Hi Joe,

This afternoon we installed RHEL7.2 with same HW, and yes this issue could be reproduced. Its behavior is same as RHEL7.3.

Comment 10 Huaisheng 2016-10-11 07:20:28 UTC

Do you have anything updated for this issue?

Comment 13 Futur Fusionneur 2016-10-19 05:38:53 UTC

[root@centos~]# cat /etc/*-release | grep release | head -1
CentOS Linux release 7.2.1511 (Core)

[root@centos~]# rpm -qa | grep crash
crash-7.1.2-3.el7_2.1.x86_64

[root@centfusion ~]# uname -a
Linux centfusion 3.10.0-327.36.2.el7.x86_64 #1 SMP Mon Oct 10 23:08:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


Bug still present.

Comment 14 Futur Fusionneur 2016-10-19 05:39:58 UTC

(In reply to Futur Fusionneur from comment #13)
> [root@centos~]# cat /etc/*-release | grep release | head -1
> CentOS Linux release 7.2.1511 (Core)
> 
> [root@centos~]# rpm -qa | grep crash
> crash-7.1.2-3.el7_2.1.x86_64
> 
> [root@centfusion ~]# uname -a
> Linux centfusion 3.10.0-327.36.2.el7.x86_64 #1 SMP Mon Oct 10 23:08:37 UTC
> 2016 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> Bug still present.

Disregard crash package, it's colord:

[root@centfusion ~]# rpm -qa | grep colord
colord-1.2.7-2.el7.x86_64
colord-libs-1.2.7-2.el7.x86_64
colord-gtk-0.1.25-4.el7.x86_64
compat-libcolord1-1.0.4-1.el7.x86_64

Comment 16 Huaisheng 2016-12-03 02:26:36 UTC

This defect has been reported more than 3 months. If you think which is harmless for server products, please let us know it. We need to close this defect ASAP.

Comment 17 Joseph Kachuck 2016-12-05 15:55:26 UTC

Hello Lenovo,
I am requesting an update on this issue from engineering.

Thank You
Joe Kachuck

Comment 18 Richard Hughes 2016-12-06 09:34:13 UTC

(In reply to Huaisheng from comment #0)
> Found there were colord: (colord:17646): Cd-WARNING **: failed to get edid
> data: EDID length is too small

The hardware that is attached is returning an EDID data block that is too small. An EDID data blob has to be at least 128 bytes in length: https://en.wikipedia.org/wiki/Extended_Display_Identification_Data

If you remove whatever faulty display is attached then colord will no longer print this warning message. If you're running the server with a "dumb" keyboard/mouse/display switcher that may be mangling the EDID request.

Comment 19 Richard Hughes 2017-01-10 20:19:29 UTC

Closing as no further input has been provided. I don't think it's a bug to log invalid EDID entries from faulty hardware.