From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107518] polaris powerplay init fails: There must be 1 or more PCIE levels defined in PPTable
Date: Tue, 07 Aug 2018 20:34:50 +0000 [thread overview]
Message-ID: <bug-107518-502-clGSi5bQQg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107518-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 446 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107518
--- Comment #2 from Shawn Anastasio <shawnanastasio@yahoo.com> ---
Upon further testing, the issue seems to go away when the firmware is removed
from petitboot, preventing it from initializing the card before the host OS.
This indicates that it may have something to do with the GPU being initialized
twice.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1307 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
next prev parent reply other threads:[~2018-08-07 20:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 19:15 [Bug 107518] polaris powerplay init fails: There must be 1 or more PCIE levels defined in PPTable bugzilla-daemon
2018-08-07 19:55 ` bugzilla-daemon
2018-08-07 20:34 ` bugzilla-daemon [this message]
2018-08-07 21:24 ` bugzilla-daemon
2018-08-08 3:47 ` bugzilla-daemon
2018-08-08 15:04 ` bugzilla-daemon
2018-08-10 6:06 ` bugzilla-daemon
2018-08-10 14:46 ` bugzilla-daemon
2018-08-25 19:19 ` bugzilla-daemon
2018-08-26 0:08 ` bugzilla-daemon
2018-08-27 13:56 ` bugzilla-daemon
2018-08-29 9:09 ` bugzilla-daemon
2018-08-29 13:33 ` bugzilla-daemon
2018-10-27 5:29 ` bugzilla-daemon
2018-10-29 19:04 ` bugzilla-daemon
2019-11-19 8:46 ` 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-107518-502-clGSi5bQQg@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;
as well as URLs for NNTP newsgroup(s).