From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 110371] HP Dreamcolor display *Error* No EDID read Date: Thu, 18 Apr 2019 15:29:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1868367868==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id EA3E96E169 for ; Thu, 18 Apr 2019 15:29:24 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1868367868== Content-Type: multipart/alternative; boundary="15556013640.DEbeF2.11108" Content-Transfer-Encoding: 7bit --15556013640.DEbeF2.11108 Date: Thu, 18 Apr 2019 15:29:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D110371 --- Comment #5 from Nicholas Kazlauskas --- (In reply to Michel D=C3=A4nzer from comment #4) > (In reply to Nicholas Kazlauskas from comment #3) > > It's hitting the "." as part of the video mode and erroring out because= DRM > > doesn't consider it a valid character. >=20 > Or maybe there's two separate issues? Failure to parse the mode name > shouldn't affect whether or not DC picks up EDID, should it? I suppose that doesn't actually influence whether the EDID has been read or= is valid. So that's a different bug. The "No EDID read." error comes from the result from drm_get_edid(...) being NULL, however. While we're responsible for the actual transfers to and from the receiver t= he actual logic is shared there between drivers. (In reply to Babblebones from comment #2) > Created attachment 143957 [details] > Dmesg output from an affected kernel >=20 > Here is the issue, you can see > [ 1.335096] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read. >=20 > Which is about where the display turns into fruit salad. > Please let me know if I can submit any more debug info that would assist!= I > am very much in need of running a newer kernel. Can you post a dmesg log with drm.debug=3D4 as part of your kernel boot parameters? --=20 You are receiving this mail because: You are the assignee for the bug.= --15556013640.DEbeF2.11108 Date: Thu, 18 Apr 2019 15:29:24 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 5 on bug 11037= 1 from Nicholas Kazlauskas<= /a> 
(In reply to Michel D=C3=A4nzer from comment #4)
> (In reply to Nicholas Kazlauskas from comment #3)
> > It's hitting the "." as part of the video mode and erro=
ring out because DRM
> > doesn't consider it a valid character.
>=20
> Or maybe there's two separate issues? Failure to parse the mode name
> shouldn't affect whether or not DC picks up EDID, should it?

I suppose that doesn't actually influence whether the EDID has been read or=
 is
valid. So that's a different bug.

The "No EDID read." error comes from the result from drm_get_edid=
(...) being
NULL, however.

While we're responsible for the actual transfers to and from the receiver t=
he
actual logic is shared there between drivers.

(In reply to Babblebones from comme=
nt #2)
> Created attachment 143957 [details]=

> Dmesg output from an affected kernel
>=20
> Here is the issue, you can see
> [    1.335096] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.
>=20
> Which is about where the display turns into fruit salad.
> Please let me know if I can submit any more debug info that would assi=
st! I
> am very much in need of running a newer kernel.

Can you post a dmesg log with drm.debug=3D4 as part of your kernel boot
parameters?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15556013640.DEbeF2.11108-- --===============1868367868== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1868367868==--