dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110371] HP Dreamcolor display *Error* No EDID read
Date: Thu, 18 Apr 2019 15:29:25 +0000	[thread overview]
Message-ID: <bug-110371-502-zhUcOXQ09a@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110371-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1425 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110371

--- Comment #5 from Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> ---
(In reply to Michel Dänzer 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.
> 
> 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 the
actual logic is shared there between drivers.

(In reply to Babblebones from comment #2)
> Created attachment 143957 [details]
> Dmesg output from an affected kernel
> 
> Here is the issue, you can see
> [    1.335096] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.
> 
> 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=4 as part of your kernel boot
parameters?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2683 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-04-18 15:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10  3:38 [Bug 110371] HP Dreamcolor display *Error* No EDID read bugzilla-daemon
2019-04-10  7:38 ` bugzilla-daemon
2019-04-13  2:14 ` bugzilla-daemon
2019-04-18 14:40 ` bugzilla-daemon
2019-04-18 14:59 ` bugzilla-daemon
2019-04-18 15:11 ` bugzilla-daemon
2019-04-18 15:29 ` bugzilla-daemon [this message]
2019-04-19 17:59 ` bugzilla-daemon
2019-05-02  3:09 ` bugzilla-daemon
2019-05-05 17:48 ` bugzilla-daemon
2019-05-05 18:31 ` bugzilla-daemon
2019-05-10 22:32 ` bugzilla-daemon
2019-05-15  5:02 ` bugzilla-daemon
2019-10-15  2:28 ` 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=bug-110371-502-zhUcOXQ09a@http.bugs.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