[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #36 from Rev (r...@pop.ms) --- I still get around 700 error logs per day on my 24/7 PC. amdgpu :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.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #35 from Emre (ereno...@gmail.com) --- Hi Artem, I did not see my issue (stated above) since the last few kernel releases. I'm now at 6.9.9-arch1-1. These days it seemed reliable to me. Sometimes I'm losing "4k resolution" but that may be due to the Monitor not the driver (power cycling monitor fixes it). -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added CC||a...@gmx.com --- Comment #34 from Artem S. Tashkinov (a...@gmx.com) --- If no one wants this bug to be fixed, I will close the freedesktop issue. The AMD team can't do much if the affected people are not willing to collaborate. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/drm/amd/-/issues/3494 --- Comment #33 from Artem S. Tashkinov (a...@gmx.com) --- Please take it to here: https://gitlab.freedesktop.org/drm/amd/-/issues/3494 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #32 from Artem S. Tashkinov (a...@gmx.com) --- All the amdgpu hackers are here, please refile and attach dmesg for 6.10 if you're still affected: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #31 from gabriel barros (gabrielbarro...@gmail.com) --- Created attachment 306574 --> https://bugzilla.kernel.org/attachment.cgi?id=306574=edit 6.9.9 kernel logs, rebooting with monitor connected. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #30 from gabriel barros (gabrielbarro...@gmail.com) --- Created attachment 306573 --> https://bugzilla.kernel.org/attachment.cgi?id=306573=edit kernel logs, failure when attaching HDMI cable to long running system Adding to Comment 29. I still get the EDID errors even when it "works" after a reboot-with-monitor-already-plugged. Here are the logs. First the log for the failure, which happens when i plug in the monitor in a long running system -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 gabriel barros (gabrielbarro...@gmail.com) changed: What|Removed |Added CC||gabrielbarro...@gmail.com --- Comment #29 from gabriel barros (gabrielbarro...@gmail.com) --- This bug doesn't have much trigger information. But i arrived here with a completely different system than what is on the reports (6650U iGPU, with both a DP monitor and a hdmi1.2 and 1.4 TVs). Reboot as mentioned in Comment 25 "solved" it. The link on Comment 18 is dead, in case anyone want to share the kernel options here. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #28 from Rev (r...@pop.ms) --- I share that concern. Can the OP create a new report with a recent kernel and updated logs, maybe with a link to this report? That would be wonderful! By the way, my last comment, that the issue stops when the display is woken up is wrong. Sometimes one display suspend is enough that the issue will repeat in the logs, even if the display is "on" after that all the time. But this is rather sporadic, sometimes the errors stop, sometimes they continue. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #27 from Emre (ereno...@gmail.com) --- This makes my docked laptop almost unusable :( Once it suspends the displays, there's no coming back. I'd need to undock, and hope it recovers. After undocking, re-docking the USB-C hub does not help, external displays mostly dont come back. Needs reboot :( I wonder if there's a way to change severity/importance of this bug, I'm worried that nobody looks at it as it's tagged 4.19 and 5.x while it exists in the latest version of kernel. This effects usability big time. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #26 from Rev (r...@pop.ms) --- My display is connected via HDMI and on 6.2.10 mainline this error is coming up all 2 to 3 minutes in the logs. A relation to a display suspend is quite right in my eyes, because it stops when the display is woken up and starts again on display suspend. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Emre (ereno...@gmail.com) changed: What|Removed |Added CC||ereno...@gmail.com --- Comment #25 from Emre (ereno...@gmail.com) --- I still see this error in 6.2.10-arch1-1. It happens for displays connected through a USB-C hub: [5.230549] EDID block 0 is all zeroes [5.230552] [drm:dc_link_add_remote_sink [amdgpu]] *ERROR* Bad EDID, status3! A suspend / resume after system boots to login screen solves the issue. But it comes back sometimes when display is suspended due to idle or other system suspend/resume cycles. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Rev (r...@pop.ms) changed: What|Removed |Added CC||r...@pop.ms --- Comment #24 from Rev (r...@pop.ms) --- Issue is back in 5.17.9 (and 8), AMD 5600G, Mesa 22.2~git2205170600.fffafa~oibaf~f, so its 4 years now? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #23 from chrisk...@goldmail.de --- Update: We are now at Kernel 5.11 and this problem is still not fixed. I am stuck at 5.8 + manually entering the EDID on startup. When 5.8 gets too outdated for me, I will buy a new monitor. I guess we cannot expect any fix after almost 3 years. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #22 from Jay Tuckey (jay@tuckey.email) --- @Sebastien that could well be the case. The screen works fine under windows, but it could be that they are working around bad EDID data? Is there any way I can validate if the EDID is bad? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #21 from Sebastien Bernard (sbern...@nerim.net) --- The more I think about it, the more it seems to be related only to this monitor. I think the 4.19 kernel closed a bug and is rejectiting the EDID reported by this screen. If someone could validate this EDID is correct, it'll be of great help. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #20 from Jay Tuckey (jay@tuckey.email) --- Hi, I'm also running into this issue, using an RX Vega 64 with an Asus ROG display. Let me know if there's any logs or testing that I can do to assist. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #19 from xavier B (xavi...@gmail.com) --- hi! I had this issue for a longtime. And then, I recently got a new hdmi cable and never had the error since! (or at least symptoms of it: the pc having trouble to enable the display after a warm reboot, and having to do a 'really' cold reboot by turning the pc off for a few minutes to get it back. I haven't been checking the logs extensively since it now works...) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #18 from chrisk...@goldmail.de --- A short update: In the meantime I am adding the modeline for my monitor manualy. The automated solution is a 10-monitor.conf like in this thread: https://archived.forum.manjaro.org/t/stuck-at-low-display-resolution/115976 This works until Kernel 5.8. With Kernel >= 5.9 my monitor doesn't accept the modeline anymore. Since this problem has been reported 2 years ago and nothing happened, I am wondering if it will ever be fixed. Let me know how I can follow up/contribute to fix this. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 C0rn3j (spleefe...@gmail.com) changed: What|Removed |Added CC||spleefe...@gmail.com --- Comment #17 from C0rn3j (spleefe...@gmail.com) --- Created attachment 292811 --> https://bugzilla.kernel.org/attachment.cgi?id=292811=edit 5.8 dmesg RX 580 I believe am hitting the same issue. I have a DP monitor ACER XB270HAbprz and it is stuck in 640x480 on my RX 580. This is on Linux 5.8. On monitor replug this relevant line pops up: [drm:dc_link_detect_helper [amdgpu]] *ERROR* No EDID read. This same monitor with the same cable works great on GTX 970 and GTX 1080 Ti under Nvidia 455.23.04. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Mike Starr (starrten...@gmail.com) changed: What|Removed |Added CC||starrten...@gmail.com --- Comment #16 from Mike Starr (starrten...@gmail.com) --- I have traced my personal version of this bug down to my Acer monitor and Logitech gamepad. Both are detected, but only the monitor works. The error spits out toward the end of dmesg about ten times in a row, twice. Thank you. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #15 from Ivan Molodetskikh (yalt...@gmail.com) --- I managed to force the kernel to use the EDID extracted via get-edid on kernel 4.18 thanks to https://bugzilla.kernel.org/show_bug.cgi?id=199799#c4 . The trick was to add video=DP-4:e to the kernel parameters, so in my case the complete addition looks like: drm.edid_firmware=DP-4:edid/ASUS_VG248QE.bin video=DP-4:e ASUS_VG248QE.bin was extracted with get-edid on kernel 4.18 and placed in /usr/lib/firmware/edid/. With this in place, I can use my monitor fine on the latest kernel (5.5.5). Without this, I have the exact same issue on 5.5.5. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #14 from chrisk...@goldmail.de --- *** Bug 205987 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 chrisk...@goldmail.de changed: What|Removed |Added CC||chrisk...@goldmail.de --- Comment #13 from chrisk...@goldmail.de --- Same here with Acer XB240H and AMD Vega 56: https://bugzilla.kernel.org/show_bug.cgi?id=205987 All Kernels >4.15 have this -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #12 from Sebastien Bernard (sbern...@nerim.net) --- I wonder if it's not a bad EDID from the monitor. Anyway, that's a regression from 4.18. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 sebastian.lars...@protonmail.com changed: What|Removed |Added CC||sebastian.larsson@protonmai ||l.com --- Comment #11 from sebastian.lars...@protonmail.com --- Been struggling with this issue for quite some time Is there any progress made? ASUS ROG Swift PG278Q R9 380X 5.4.0-rc1linux-5.4-rc1 [2.776432] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #10 from Daniel Andersson (engyw...@gmail.com) --- Is this going to get fixed? -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Daniel Andersson (engyw...@gmail.com) changed: What|Removed |Added Kernel Version|4.19 4.20 5.0-rc1 5.0-rc3 |4.19 4.20 5.0-rc1 5.0-rc3, ||5.1-rc3 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Sebastien Bernard (sbern...@nerim.net) changed: What|Removed |Added CC||sbern...@nerim.net --- Comment #9 from Sebastien Bernard (sbern...@nerim.net) --- Same here RX480 and ASUS PG278Q also. My archlinux is stuck at 4.18.16 since october 2018. Is there a workaround or someone that is looking at this bug ? It's been broken from 4.19 up to 5.0. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #8 from Elliot Thomas (e.singularity...@gmail.com) --- Created attachment 280777 --> https://bugzilla.kernel.org/attachment.cgi?id=280777=edit dmesg, amd-staging-drm-next-git (d0333a48e54fdcfdae5e378acd898a680967e939) -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Elliot Thomas (e.singularity...@gmail.com) changed: What|Removed |Added CC||e.singularity...@gmail.com --- Comment #7 from Elliot Thomas (e.singularity...@gmail.com) --- Same here, RX580 and an ASUS PG278Q monitor, also with G-Sync support. A different DisplayPort monitor (without G-Sync) worked perfectly. I've noticed someone else with the same monitor having this issue over on the freedesktop bug tracker: https://bugs.freedesktop.org/show_bug.cgi?id=108806 Interestingly, in more recent kernels, the affected monitor appears to flash rapidly. I still see the EDID read fail in this case. I'll try and grab a dmesg of this at some point. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #6 from Daniel Andersson (engyw...@gmail.com) --- Created attachment 280701 --> https://bugzilla.kernel.org/attachment.cgi?id=280701=edit 5.0-rc3 drm.debug=0x4 This is still an issue on 5.0-rc3. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Daniel Andersson (engyw...@gmail.com) changed: What|Removed |Added Kernel Version|4.19|4.19 4.20 5.0-rc1 5.0-rc3 Regression|No |Yes -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Ivan Molodetskikh (yalt...@gmail.com) changed: What|Removed |Added CC||yalt...@gmail.com --- Comment #5 from Ivan Molodetskikh (yalt...@gmail.com) --- Created attachment 280619 --> https://bugzilla.kernel.org/attachment.cgi?id=280619=edit 4.20 log I'm hitting the same issue with one of my monitors (ASUS VG248QE, G-Sync modded). I tried extracting EDID from kernel 4.18 and forcing it with drm.edid_firmware as you can see in the log, but that doesn't seem to do anything. My GPU is AMD RX 580. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #4 from Daniel Andersson (engyw...@gmail.com) --- Created attachment 280261 --> https://bugzilla.kernel.org/attachment.cgi?id=280261=edit 4.20 didn't fix this Still an issue on 4.20 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #3 from Daniel Andersson (engyw...@gmail.com) --- Any progress on this issue? -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #2 from Daniel Andersson (engyw...@gmail.com) --- Created attachment 279133 --> https://bugzilla.kernel.org/attachment.cgi?id=279133=edit 4.19 dmesg dmesg attached -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #1 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) --- The revert was only supposed to apply to 4.18 and below, there should be a series of patches that fixes this for 4.19. Please post an updated dmesg log for your 4.19 kernel. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
