All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216583] New: [AMDGPU] Black screen after resume + Failed to pin framebuffer -19
Date: Fri, 14 Oct 2022 01:05:16 +0000	[thread overview]
Message-ID: <bug-216583-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 216583
           Summary: [AMDGPU] Black screen after resume + Failed to pin
                    framebuffer -19
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.0.1
          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: contato-myghi63@protonmail.com
        Regression: No

Created attachment 302996
  --> https://bugzilla.kernel.org/attachment.cgi?id=302996&action=edit
System Log

After upgrading the kernel from 5.19.13 to 6.0.1, my screen goes black after
resuming the system. Switching the TTY to another one and going back "fixes"
the issue.
My GPU: RX 5500XT 8GB (desktop)
OS: Arch Linux

I also tried using the kernel argument amdgpu.dc=0 but this freezes the screen
on early boot (radeon and amdgpu modules are stored on initial ramdisk)

On attachment, there's relevant errors from line 1320!

-- 
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:[~2022-10-14  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  1:05 bugzilla-daemon [this message]
2022-10-14  1:07 ` [Bug 216583] [AMDGPU] Black screen after resume + Failed to pin framebuffer -19 bugzilla-daemon
2022-10-14 11:05 ` 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-216583-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.