All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200695] New: Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected)
Date: Tue, 31 Jul 2018 18:32:58 +0000	[thread overview]
Message-ID: <bug-200695-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 200695
           Summary: Blank screen on RX 580 with amdgpu.dc=1 enabled (no
                    displays detected)
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.18.0-rc7
          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: claude@mathr.co.uk
        Regression: No

Created attachment 277633
  --> https://bugzilla.kernel.org/attachment.cgi?id=277633&action=edit
dmesg after boot with amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6

When amdgpu.dc=1 is initialized at boot, the console goes blank as it thinks
all displays are disconnected.  Xorg is not able to enable the display either. 
With amdgpu.dc=0 all is fine.  Tried with various (mostly Debian) kernels from
4.16 through 4.18~rc4, all have the issue.  I built a 4.18~rc7 from kernel.org
to rule out Debian patches being the issue and will provide logs.

-- 
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-07-31 18:32 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 18:32 bugzilla-daemon [this message]
2018-07-31 18:33 ` [Bug 200695] Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected) bugzilla-daemon
2018-07-31 18:34 ` bugzilla-daemon
2018-07-31 18:37 ` bugzilla-daemon
2018-07-31 18:37 ` bugzilla-daemon
2018-07-31 18:38 ` bugzilla-daemon
2018-08-28 15:40 ` bugzilla-daemon
2018-08-28 15:42 ` bugzilla-daemon
2018-09-06  6:51 ` bugzilla-daemon
2018-09-10 13:45 ` bugzilla-daemon
2018-09-17 17:46 ` bugzilla-daemon
2018-09-17 18:09 ` bugzilla-daemon
2018-09-18  2:10 ` bugzilla-daemon
2018-09-18 13:43 ` bugzilla-daemon
2018-09-18 15:02 ` bugzilla-daemon
2018-10-01 17:30 ` bugzilla-daemon
2018-10-10 21:16 ` bugzilla-daemon
2018-10-22 18:52 ` bugzilla-daemon
2018-11-06 16:13 ` bugzilla-daemon
2018-11-13 19:54 ` bugzilla-daemon
2018-11-19 18:15 ` bugzilla-daemon
2018-12-04 23:12 ` bugzilla-daemon
2018-12-28  6:07 ` bugzilla-daemon
2019-01-12 11:18 ` bugzilla-daemon
2019-01-13 19:35 ` bugzilla-daemon
2019-02-25 17:51 ` bugzilla-daemon
2019-02-26 16:43 ` bugzilla-daemon
2019-02-27 12:42 ` bugzilla-daemon
2019-03-07 15:42 ` bugzilla-daemon
2019-03-07 16:26 ` bugzilla-daemon
2019-03-07 16:57 ` bugzilla-daemon
2019-04-02 16:38 ` bugzilla-daemon
2019-04-02 16:39 ` bugzilla-daemon
2019-09-20 11:22 ` bugzilla-daemon
2019-11-05 14:07 ` bugzilla-daemon
2019-12-16 21:43 ` bugzilla-daemon
2019-12-16 23:52 ` bugzilla-daemon
2020-02-15 14:42 ` bugzilla-daemon
2020-02-16 13:47 ` bugzilla-daemon
2020-02-16 21:12 ` bugzilla-daemon
2020-05-08 10:55 ` bugzilla-daemon
2020-05-08 15:12 ` bugzilla-daemon
2020-05-08 18:20 ` bugzilla-daemon
2020-05-30 19:22 ` bugzilla-daemon
2020-06-16 23:39 ` bugzilla-daemon
2020-06-17  2:24 ` bugzilla-daemon
2020-06-17  3:11 ` bugzilla-daemon
2020-06-28  9:25 ` bugzilla-daemon
2020-06-28  9:26 ` bugzilla-daemon
2020-06-28  9:27 ` bugzilla-daemon
2021-04-06  7:51 ` 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-200695-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.