dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208573] Black screen on boot if two displays plugged in with NAVI 10
Date: Mon, 10 Aug 2020 15:55:25 +0000	[thread overview]
Message-ID: <bug-208573-2300-k66VNzJj8k@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208573-2300@https.bugzilla.kernel.org/>

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

--- Comment #9 from Thomas Langkamp (thomas.langkamp@medicalschool-hamburg.de) ---
Yes. With the new BIOS this is reproducible only with XMP enabled.

In the other bugreport I read about

amdgpu.ppfeaturemask=0xffffbffd

I just tried it. Until now this seems to fix it, even with XMP profile 
enabled! I will report back if I get a black screen again.
As far as I know with 2 monitors attached the VRAM is always clocked 
high, so it makes sense that disabling the VRAM power management through 
this featuremask works around the issue. But surely a proper fix would 
be appreciated.

Am 10.08.20 um 16:33 schrieb bugzilla-daemon@bugzilla.kernel.org:
> https://bugzilla.kernel.org/show_bug.cgi?id=208573
> 
> --- Comment #8 from Alex Deucher (alexdeucher@gmail.com) ---
> Do you only get the MCE errors when you set the XMP profile?
>

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

  parent reply	other threads:[~2020-08-10 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 18:36 [Bug 208573] New: Black screen on boot if two displays plugged in with NAVI 10 bugzilla-daemon
2020-07-15 18:50 ` [Bug 208573] " bugzilla-daemon
2020-07-15 19:01 ` bugzilla-daemon
2020-07-15 19:01 ` bugzilla-daemon
2020-07-16 17:07 ` bugzilla-daemon
2020-08-10 11:46 ` bugzilla-daemon
2020-08-10 11:47 ` bugzilla-daemon
2020-08-10 12:06 ` bugzilla-daemon
2020-08-10 12:10 ` bugzilla-daemon
2020-08-10 14:33 ` bugzilla-daemon
2020-08-10 15:55 ` bugzilla-daemon [this message]
2020-08-10 20:38 ` bugzilla-daemon
2020-08-10 21:14 ` bugzilla-daemon
2020-09-03  6:06 ` bugzilla-daemon
2021-05-23  2:34 ` bugzilla-daemon
2021-05-24 18:03 ` 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-208573-2300-k66VNzJj8k@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 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).