All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108781] 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init
Date: Sun, 02 Dec 2018 15:53:47 +0000	[thread overview]
Message-ID: <bug-108781-502-0tUQOqhrBT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108781-502@http.bugs.freedesktop.org/>


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

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

--- Comment #32 from Shecks <shecks@gmail.com> ---
(In reply to freedesktop from comment #27)
> OK there seems to be something screwy going on with the amdgpu.dpm option -
> if that's set to 0, it still results in a blank screen. It has to be removed
> entirely from the kernel command line for boot to work for me on 4.19.
> 
> I'm not sure if that's a different bug or not, but can anyone who had
> success with removing the option, also test with amdgpu.dpm=0 to see if it
> still results in a blank screen?
> 
> Also, are FD BZ email notifications broken for anyone else?

I can confirm that attempting to boot with either amdgpu.dpm=0 or amdgpu.dpm=1
results in the same black screen issue on my PC

I am now running Fedora 29 with kernel 4.19.5 (MSI R9 390 8GB Gaming GPU) and
the only way to boot is by completely removing the amdgpu.dpm kernel parameter.

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

[-- Attachment #1.2: Type: text/html, Size: 2030 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-12-02 15:53 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-17 21:25 [Bug 108781] 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init bugzilla-daemon
2018-11-17 21:26 ` bugzilla-daemon
2018-11-17 21:26 ` bugzilla-daemon
2018-11-17 21:34 ` bugzilla-daemon
2018-11-19 15:01 ` bugzilla-daemon
2018-11-19 17:25 ` bugzilla-daemon
2018-11-20  2:26 ` bugzilla-daemon
2018-11-20 12:50 ` bugzilla-daemon
2018-11-20 14:35 ` bugzilla-daemon
2018-11-20 20:20 ` bugzilla-daemon
2018-11-21  0:06 ` bugzilla-daemon
2018-11-21  7:52 ` bugzilla-daemon
2018-11-21  9:48 ` bugzilla-daemon
2018-11-22  0:13 ` bugzilla-daemon
2018-11-22  0:15 ` bugzilla-daemon
2018-11-22  0:15 ` bugzilla-daemon
2018-11-22  0:48 ` bugzilla-daemon
2018-11-22  1:38 ` bugzilla-daemon
2018-11-22 17:01 ` bugzilla-daemon
2018-11-22 18:56 ` bugzilla-daemon
2018-11-23  9:42 ` bugzilla-daemon
2018-11-23 14:42 ` bugzilla-daemon
2018-11-23 21:46 ` bugzilla-daemon
2018-11-23 22:42 ` bugzilla-daemon
2018-11-23 22:43 ` bugzilla-daemon
2018-11-25 19:08 ` bugzilla-daemon
2018-11-27 17:11 ` bugzilla-daemon
2018-11-28 11:28 ` bugzilla-daemon
2018-11-28 11:45 ` bugzilla-daemon
2018-11-28 14:46 ` bugzilla-daemon
2018-12-02  6:34 ` bugzilla-daemon
2018-12-02  6:44 ` bugzilla-daemon
2018-12-02 15:53 ` bugzilla-daemon [this message]
2018-12-03  3:07 ` bugzilla-daemon
2018-12-03 13:16 ` bugzilla-daemon
2018-12-03 13:26 ` bugzilla-daemon
2018-12-30 22:55 ` bugzilla-daemon
2018-12-31 15:08 ` bugzilla-daemon
2019-01-05 13:28 ` bugzilla-daemon
2019-01-11  0:04 ` bugzilla-daemon
2019-11-19  9:04 ` 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-108781-502-0tUQOqhrBT@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.