All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93217] [tonga] [powerplay] Radon M395X isn't initialised with the powerplay branch
Date: Tue, 15 Dec 2015 00:34:43 +0000	[thread overview]
Message-ID: <bug-93217-502-IC0xnkEs63@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93217-502@http.bugs.freedesktop.org/>


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

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

Mike Lothian <mike@fireburn.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #120285|0                           |1
        is obsolete|                            |
 Attachment #120501|0                           |1
        is obsolete|                            |

--- Comment #16 from Mike Lothian <mike@fireburn.co.uk> ---
Created attachment 120507
  --> https://bugs.freedesktop.org/attachment.cgi?id=120507&action=edit
Powerplay working

I still have to set pcie_dpm_key_disabled = 1 

I had to turn of pid cgroups for some reason

I also had to turn off runpm, it seems the card is initialised the first time
then when it's powered back up has a hissy fit

I tested Metro 2033 Redux so I know I was definitely running on Tonga but I
locked up the system setting everything to max

Progress :D

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

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

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

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

  parent reply	other threads:[~2015-12-15  0:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 18:36 [Bug 93217] [tonga] [powerplay] Radon M395X isn't initialised with the powerplay branch bugzilla-daemon
2015-12-02 18:36 ` bugzilla-daemon
2015-12-02 18:37 ` bugzilla-daemon
2015-12-02 18:37 ` bugzilla-daemon
2015-12-05  2:15 ` bugzilla-daemon
2015-12-07 19:33 ` bugzilla-daemon
2015-12-07 19:33 ` bugzilla-daemon
2015-12-07 22:05 ` bugzilla-daemon
2015-12-07 22:11 ` bugzilla-daemon
2015-12-11 13:02 ` bugzilla-daemon
2015-12-11 17:43 ` bugzilla-daemon
2015-12-11 18:37 ` bugzilla-daemon
2015-12-14 15:51 ` bugzilla-daemon
2015-12-14 19:01 ` bugzilla-daemon
2015-12-14 21:05 ` bugzilla-daemon
2015-12-14 22:43 ` bugzilla-daemon
2015-12-14 23:45 ` bugzilla-daemon
2015-12-15  0:34 ` bugzilla-daemon [this message]
2015-12-15  0:36 ` bugzilla-daemon
2015-12-19  3:11 ` bugzilla-daemon
2015-12-19  3:26 ` bugzilla-daemon
2015-12-20 14:37 ` bugzilla-daemon
2015-12-21 21:25 ` bugzilla-daemon
2015-12-21 21:35 ` bugzilla-daemon
2016-01-21 14:42 ` bugzilla-daemon
2016-01-21 14:43 ` bugzilla-daemon
2016-01-21 19:43 ` bugzilla-daemon
2016-01-22  0:31 ` bugzilla-daemon
2016-01-22 19:14 ` bugzilla-daemon
2016-01-27 23:42 ` bugzilla-daemon
2016-01-28  0:31 ` bugzilla-daemon
2016-02-06  5:14 ` bugzilla-daemon
2016-02-22 17:20 ` bugzilla-daemon
2016-02-22 22:54 ` bugzilla-daemon
2016-04-15 17:51 ` bugzilla-daemon
2016-05-31 18:37 ` bugzilla-daemon
2016-05-31 18:39 ` 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-93217-502-IC0xnkEs63@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.