All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106940] Black screen on KMS with 4.18.0-rc1 with Kaveri+Topaz, amdgpu, dc=1
Date: Wed, 26 Sep 2018 08:39:10 +0000	[thread overview]
Message-ID: <bug-106940-502-anj9HL4C86@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106940-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 681 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106940

--- Comment #41 from Andrey Arapov <andrey.arapov@nixaid.com> ---
Not sure if that helps, but could you try reverting this commit?
https://github.com/torvalds/linux/commit/e03fd3f300f6184c1264186a4c815e93bf658abb

My MacBookPro Mid 2017 started to experience the black screen issue since
4.18.0-rc1 up to 4.19.0-rc4 (and probably higher). Having that commit reverted
has resolved the black screen issue I had, allowing me to use amdgpu.dc=1
again. 


Refs:

- https://github.com/Dunedan/mbp-2016-linux/issues/73#issuecomment-422397681

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1692 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-09-26  8:39 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-17 11:47 [Bug 106940] Black screen on KMS with 4.18.0-rc1 with Kaveri+Topaz, amdgpu, dc=1 bugzilla-daemon
2018-06-17 11:52 ` bugzilla-daemon
2018-06-18  8:30 ` bugzilla-daemon
2018-06-18  8:47 ` bugzilla-daemon
2018-06-18 11:10 ` bugzilla-daemon
2018-06-18 11:11 ` bugzilla-daemon
2018-06-18 11:12 ` bugzilla-daemon
2018-06-18 11:13 ` bugzilla-daemon
2018-06-18 11:13 ` bugzilla-daemon
2018-06-18 11:13 ` bugzilla-daemon
2018-06-18 11:14 ` bugzilla-daemon
2018-06-18 14:23 ` bugzilla-daemon
2018-06-18 15:31 ` bugzilla-daemon
2018-06-19 20:50 ` bugzilla-daemon
2018-06-20  7:50 ` bugzilla-daemon
2018-06-20  8:39 ` bugzilla-daemon
2018-06-20  9:33 ` bugzilla-daemon
2018-06-20 12:35 ` bugzilla-daemon
2018-06-20 15:12 ` bugzilla-daemon
2018-06-20 17:11 ` bugzilla-daemon
2018-06-20 17:25 ` bugzilla-daemon
2018-06-20 20:59 ` bugzilla-daemon
2018-06-20 21:00 ` bugzilla-daemon
2018-06-21  8:48 ` bugzilla-daemon
2018-06-26 16:44 ` bugzilla-daemon
2018-06-26 17:23 ` bugzilla-daemon
2018-07-01 18:46 ` bugzilla-daemon
2018-08-06 10:08 ` bugzilla-daemon
2018-08-13 12:26 ` bugzilla-daemon
2018-08-15 18:18 ` bugzilla-daemon
2018-08-15 18:22 ` bugzilla-daemon
2018-08-15 19:52 ` bugzilla-daemon
2018-08-15 19:54 ` bugzilla-daemon
2018-08-15 19:55 ` bugzilla-daemon
2018-08-15 20:21 ` bugzilla-daemon
2018-08-15 20:30 ` bugzilla-daemon
2018-08-15 22:00 ` bugzilla-daemon
2018-08-16  6:36 ` bugzilla-daemon
2018-08-16  9:21 ` bugzilla-daemon
2018-08-16 17:53 ` bugzilla-daemon
2018-08-16 17:55 ` bugzilla-daemon
2018-08-16 18:05 ` bugzilla-daemon
2018-08-16 20:37 ` bugzilla-daemon
2018-09-26  8:39 ` bugzilla-daemon [this message]
2018-09-26 19:30 ` bugzilla-daemon
2018-09-27 13:20 ` bugzilla-daemon
2018-09-27 15:26 ` bugzilla-daemon
2019-11-19  8:41 ` 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-106940-502-anj9HL4C86@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.