All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206053] New: Lock screen Black after idle with amdgpu.dc=1
Date: Wed, 01 Jan 2020 21:25:15 +0000	[thread overview]
Message-ID: <bug-206053-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 206053
           Summary: Lock screen Black after idle with amdgpu.dc=1
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19+
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: eutychios23@gmail.com
        Regression: No

Created attachment 286565
  --> https://bugzilla.kernel.org/attachment.cgi?id=286565&action=edit
mydmesg

I am having a system with rx 550 polaris using amdgpu kernel driver and Mesa
19.3+.
when the screen gets idle locked with
lightlocker,xscreensaver,xfce4-screensaver the screen cannot get signal back
and i get a black screen. The screen lockers work because if i enter my passwd
and press enter i can login in the desktop.

Additional info: If i lock/blank the screen manually and move them mouse the
screen gets the signal back like it should.Issue happens across Debian and Arch
distributions.Monitor is connected with an hdmi 2.0 cable.

Workaround: Adding amdgpu.dc=0 in grub resolves the issue for all screen
lockers in my system, but disables amd display code.

-- 
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:[~2020-01-01 21:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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