All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201497] New: [amdgpu]: '*ERROR* No EDID read' is back in 4.19
Date: Tue, 23 Oct 2018 17:23:44 +0000	[thread overview]
Message-ID: <bug-201497-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 201497
           Summary: [amdgpu]: '*ERROR* No EDID read' is back in 4.19
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: engywook@gmail.com
        Regression: No

Hey,

I have this EDID bug again, see
https://lists.freedesktop.org/archives/amd-gfx/2018-July/023923.html

018d82e5f02ef3583411bcaa4e00c69786f46f19 seems to have gotten back in through:
# first bad commit: [d98c71dadc2d0debdb80beb5a478baf1e6f98758] Merge
drm-upstream/drm-next into drm-misc-next

/ Daniel

-- 
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

             reply	other threads:[~2018-10-23 17:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 17:23 bugzilla-daemon [this message]
2018-10-24 13:19 ` [Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19 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

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@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.