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 220304] New: [amdgpu] DisplayPort resource allocation issue (one blank screen)
Date: Tue, 01 Jul 2025 18:01:21 +0000	[thread overview]
Message-ID: <bug-220304-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 220304
           Summary: [amdgpu] DisplayPort resource allocation issue (one
                    blank screen)
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: jonas@sldr.se
        Regression: No

I have a Lenovo laptop with an AMD Ryzen 7 (7840HS) and its integrated GPU ATI
Phoenix1. The laptop is connected to a Thunderbolt 4 Dell dock (WD22TB4)
through which it is connected to two 4K screens via DisplayPort. OS is NixOS.

The problem: after updating NixOS, my kernel jumped from 6.6.something to
6.12.something-else. During boot, all screens light up and show the boot
process, but as soon as X starts one of the external screens go dark,
complaining of no signal. X, however, still thinks the screen is there, showing
it as connected and functional. Changing the screen modes around can let me
change which screen loses signal, and reducing the resolution on one of them
brings them both back on, but then no longer in 4K. Switching the system back
to the 6.6 kernel (but still in the latest NixOS version) "fixes" the issue,
and both 4K screen work again.

After some bisecting, I've narrowed down the window where this problem was
introduced to somewhere between 6.9.0 and 6.10-rc1. I also tested later kernels
(6.13 and 6.14) which all showed the same issue. Opening this report to have it
reported, while I continue bisecting and hopefully finding the rough-ish source
of the problem.

-- 
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:[~2025-07-01 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 18:01 bugzilla-daemon [this message]
2025-07-01 20:48 ` [Bug 220304] [amdgpu] DisplayPort resource allocation issue (one blank screen) bugzilla-daemon
2025-07-02 15:25 ` 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-220304-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 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).