dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
Date: Fri, 19 Jul 2024 08:55:55 +0000	[thread overview]
Message-ID: <bug-201497-2300-DxOEsfaJi1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201497-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=201497

--- Comment #36 from Rev (rev@pop.ms) ---
I still get around 700 error logs per day on my 24/7 PC. 

amdgpu 0000:06:00.0: [drm] *ERROR* No EDID read.

I am using the standard-kernel of ubuntu 24.04 LTS now (6.8.0-36-generic), with
the standard mesa (24.0.9) drivers that come with the OS.

Display standby's and wake-up's work as intended tho in ubuntu 24.04. Putting
the whole system on standby and waking it up works since the change from ubuntu
22.04 to 24.04. 

So for me it is not an issue about a function. It is an issue that is most
prominent in the logs of ubuntu. If I did not review the logs I would never had
known about wake-up issues in 24.04, that was different in 22.04. Putting the
PC in standby in 22.04 meant never waking up the display again and the need of
a cold boot.

But an average of 700 error messages per day means there is something not
working right, imo. And since that is a very, very old issue since a far older
kernel version, and a lot of AMD gpu users out there, I would like to help. But
I am not a tech expert, just a user who can read stuff and do stuff a bit
better that an average user. So please, if you want some more help from users
with that issue, please explain how we can help for a solution and I would
guess people would contribute their information to help solving this issue.

Sorry for the long winded comment.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2024-07-19  8:56 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 17:23 [Bug 201497] New: [amdgpu]: '*ERROR* No EDID read' is back in 4.19 bugzilla-daemon
2018-10-24 13:19 ` [Bug 201497] " bugzilla-daemon
2018-10-24 13:41 ` bugzilla-daemon
2018-11-30 18:19 ` bugzilla-daemon
2019-01-04 10:05 ` bugzilla-daemon
2019-01-21  9:55 ` bugzilla-daemon
2019-01-23 21:43 ` bugzilla-daemon
2019-01-23 21:44 ` bugzilla-daemon
2019-01-23 23:49 ` bugzilla-daemon
2019-01-25 23:50 ` bugzilla-daemon
2019-03-10 15:16 ` bugzilla-daemon
2019-04-02 21:29 ` bugzilla-daemon
2019-09-02 17:59 ` bugzilla-daemon
2019-10-08  4:45 ` bugzilla-daemon
2019-12-16 19:14 ` bugzilla-daemon
2020-01-03 19:25 ` bugzilla-daemon
2020-01-03 19:29 ` bugzilla-daemon
2020-02-24 12:01 ` bugzilla-daemon
2020-08-29 14:55 ` bugzilla-daemon
2020-10-04 19:09 ` bugzilla-daemon
2020-12-24 13:19 ` bugzilla-daemon
2020-12-26 10:32 ` bugzilla-daemon
2021-01-24  5:32 ` bugzilla-daemon
2021-01-24 23:08 ` bugzilla-daemon
2021-01-25  0:29 ` bugzilla-daemon
2021-02-19  9:47 ` bugzilla-daemon
2022-05-19  0:34 ` bugzilla-daemon
2023-04-08 17:26 ` bugzilla-daemon
2023-04-09 10:24 ` bugzilla-daemon
2023-04-13  9:39 ` bugzilla-daemon
2023-04-13  9:54 ` bugzilla-daemon
2024-07-16  2:22 ` bugzilla-daemon
2024-07-16  2:35 ` bugzilla-daemon
2024-07-16  2:36 ` bugzilla-daemon
2024-07-17  8:36 ` bugzilla-daemon
2024-07-17  8:42 ` bugzilla-daemon
2024-07-18 17:51 ` bugzilla-daemon
2024-07-19  6:32 ` bugzilla-daemon
2024-07-19  8:55 ` bugzilla-daemon [this message]

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-201497-2300-DxOEsfaJi1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.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).