All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 217237] New: Fail to read EDID after resuming from suspend since kernel 6.2
Date: Thu, 23 Mar 2023 21:40:12 +0000	[thread overview]
Message-ID: <bug-217237-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 217237
           Summary: Fail to read EDID after resuming from suspend since
                    kernel 6.2
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.3.0-rc3
          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: chewi@gentoo.org
        Regression: No

Created attachment 304013
  --> https://bugzilla.kernel.org/attachment.cgi?id=304013&action=edit
dmesg from 6.2.7 showing boot, suspend, resume

Since upgrading past Linux kernel 6.2, my system has been unable to read the
EDID after resuming from suspend. I got the following error:

[  135.566642] EDID block 0 is all zeroes
[  135.566831] amdgpu 0000:0f:00.0: [drm] User-defined mode not supported:
"2560x1440": 144 592000 2560 2568 2600 2666 1440 1465 1470 1543 0x60 0x9
[  135.566836] amdgpu 0000:0f:00.0: [drm] User-defined mode not supported:
"2560x1440": 144 807923 2560 2784 3072 3584 1440 1441 1444 1565 0x20 0x6

After this, the only available mode is 640x480. This happens with both my
displays, a monitor and a TV. I have a Radeon RX 6800 XT that previously worked
fine in this regard. I usually override the EDID with drm.edid_firmware, but
removing this has not helped.

I tried bisecting the issue, but perhaps it doesn't happen every single time,
as it lead my down a dead end. I also tried reverting some potential culprits,
to no avail. I can see that there were some very large EDID-related changes by
Jani Nikula for 6.2. I wasn't able to revert these, so I will CC them here.

I am happy to provide further information.

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

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

             reply	other threads:[~2023-03-23 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 21:40 bugzilla-daemon [this message]
2023-03-24  7:43 ` [Bug 217237] Fail to read EDID after resuming from suspend since kernel 6.2 bugzilla-daemon
2023-03-24  8:04 ` 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-217237-2300@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 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.