dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95306] Random Blank(black) screens on "Carrizo"
Date: Tue, 21 Nov 2017 22:21:49 +0000	[thread overview]
Message-ID: <bug-95306-502-cJ0JyuM7gJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95306-502@http.bugs.freedesktop.org/>


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

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

--- Comment #69 from Tom <tom.vycital@gmail.com> ---
(In reply to Charly from comment #68)
> Hi,
> 
> I made a fresh install of Archlinux (GNU/Linux kernel 4.13.11) on a HP
> Probook 455 G3 with A10-8700p APU and 1x8GB RAM (no dedicated GPU) with the
> default driver (amdgpu open source driver): I experience the issue described
> by Andrew who opened the thread in May 2016. The black screen appears at a
> certain step of the boot. After a cycle of suspend?resune (usually 3 or 4)
> the display turns right and is stable (if no X session is started...) I can
> confirm the issue is not linked to X since it is not installed. The only
> messages for amdgpu in journalctl are 
> 
> amdgpu: [powerplay] min_core_set_clock not set
> 
> but amdgpu.powerplay=0 is not recognized any longer:
> 
> kernel: amdgpu: unknown parameter 'powerplay' ignored.
> 
> Any (new) idea ?
> 
> Can anybody explain what will kermels 4.14 and especially 4.15 will bring us
> (carrizo users)?

There seems to be no solution. I tried several params, combinations of various
things (some even led to quite serious file system corruption) but it had no
positive effect whatsoever. Playing with powerplay/dpm etc. just made my laptop
overheat a lot.

I had some luck with amdgpu-pro in 2016, but it was even less usable. It always
booted successfully but there was mostly pinkish garbage on the screen (±75%)
although I could see the desktop at some places (±25%) and therefore somewhat
use it (login and reboot). Not sure if it is better nowadays, I think it's
worth a try.

Since this issue is here at least since 4.4 I highly doubt 4.14 or 4.15 will
bring the solution.

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

[-- Attachment #1.2: Type: text/html, Size: 2726 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:[~2017-11-21 22:21 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 20:27 [Bug 95306] Random Blank(black) screens on "Carrizo" bugzilla-daemon
2016-05-06 20:32 ` bugzilla-daemon
2016-08-05 17:31 ` bugzilla-daemon
2016-08-05 17:34 ` bugzilla-daemon
2016-08-09 19:27 ` bugzilla-daemon
2016-08-22 15:54 ` bugzilla-daemon
2016-08-22 15:56 ` bugzilla-daemon
2016-08-22 15:56 ` bugzilla-daemon
2016-08-22 15:58 ` bugzilla-daemon
2016-08-23  1:13 ` bugzilla-daemon
2016-08-23 14:11 ` bugzilla-daemon
2016-08-24  0:45 ` bugzilla-daemon
2016-08-24 17:19 ` bugzilla-daemon
2016-08-24 17:30 ` bugzilla-daemon
2016-08-24 17:39 ` bugzilla-daemon
2016-08-24 17:40 ` bugzilla-daemon
2016-08-25  6:34 ` bugzilla-daemon
2016-09-08 10:50 ` bugzilla-daemon
2016-09-09  3:29 ` bugzilla-daemon
2016-09-15 16:38 ` bugzilla-daemon
2016-10-07  1:19 ` bugzilla-daemon
2016-10-07  1:29 ` bugzilla-daemon
2016-10-07 10:51 ` bugzilla-daemon
2016-10-07 13:53 ` bugzilla-daemon
2016-10-07 13:54 ` bugzilla-daemon
2016-10-07 13:59 ` bugzilla-daemon
2016-10-07 14:00 ` bugzilla-daemon
2016-10-07 14:04 ` bugzilla-daemon
2016-10-07 14:05 ` bugzilla-daemon
2016-10-07 20:08 ` bugzilla-daemon
2016-10-08  0:31 ` bugzilla-daemon
2016-11-07 21:04 ` bugzilla-daemon
2016-11-08  3:36 ` bugzilla-daemon
2016-11-08  8:10 ` bugzilla-daemon
2016-11-08 13:35 ` bugzilla-daemon
2016-11-08 13:36 ` bugzilla-daemon
2016-11-23  2:43 ` bugzilla-daemon
2016-11-29 12:32 ` bugzilla-daemon
2016-11-29 18:40 ` bugzilla-daemon
2017-01-05 19:05 ` bugzilla-daemon
2017-01-05 19:09 ` bugzilla-daemon
2017-01-05 19:12 ` bugzilla-daemon
2017-01-05 19:14 ` bugzilla-daemon
2017-01-05 19:30 ` bugzilla-daemon
2017-01-06 17:30 ` bugzilla-daemon
2017-01-09  7:02 ` bugzilla-daemon
2017-01-09 15:16 ` bugzilla-daemon
2017-01-09 15:18 ` bugzilla-daemon
2017-01-09 15:25 ` bugzilla-daemon
2017-01-09 20:51 ` bugzilla-daemon
2017-01-09 20:54 ` bugzilla-daemon
2017-01-10  7:08 ` bugzilla-daemon
2017-01-13 20:10 ` bugzilla-daemon
2017-01-16  5:11 ` bugzilla-daemon
2017-01-24 13:48 ` bugzilla-daemon
2017-01-25  1:13 ` bugzilla-daemon
2017-01-30 20:27 ` bugzilla-daemon
2017-02-01 16:32 ` bugzilla-daemon
2017-02-10  1:18 ` bugzilla-daemon
2017-02-10 19:01 ` bugzilla-daemon
2017-02-10 19:05 ` bugzilla-daemon
2017-02-12  5:09 ` bugzilla-daemon
2017-02-22  1:02 ` bugzilla-daemon
2017-02-22  1:19 ` bugzilla-daemon
2017-03-03 22:10 ` bugzilla-daemon
2017-03-04  7:51 ` bugzilla-daemon
2017-03-04  7:56 ` bugzilla-daemon
2017-03-06 15:31 ` bugzilla-daemon
2017-03-06 19:57 ` bugzilla-daemon
2017-03-06 20:10 ` bugzilla-daemon
2017-11-21 21:57 ` bugzilla-daemon
2017-11-21 22:21 ` bugzilla-daemon [this message]
2017-12-06 16:35 ` bugzilla-daemon
2017-12-06 17:14 ` bugzilla-daemon
2017-12-06 17:17 ` bugzilla-daemon
2017-12-06 17:26 ` bugzilla-daemon
2017-12-07  5:54 ` bugzilla-daemon
2017-12-08  7:38 ` bugzilla-daemon
2017-12-11  3:19 ` bugzilla-daemon
2017-12-11 16:22 ` bugzilla-daemon
2017-12-13  1:01 ` bugzilla-daemon
2017-12-14 20:43 ` bugzilla-daemon
2017-12-19  5:10 ` bugzilla-daemon
2017-12-25 15:34 ` bugzilla-daemon
2017-12-27  9:11 ` 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-95306-502-cJ0JyuM7gJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox