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 82201] [HAWAII] GPU doesn't reclock, poor 3D performance
Date: Wed, 08 Oct 2014 18:51:29 +0000	[thread overview]
Message-ID: <bug-82201-502-xekbiCP95x@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82201-502@http.bugs.freedesktop.org/>


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

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

Kai <kai@dev.carbon-project.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #32 from Kai <kai@dev.carbon-project.org> ---
Since upgrading to the stack detailed first in bug 84570, comment #5, I have a
constantly reclocking GPU. Not sure if I missed some patch in my builds of
Alex' drm-next-3.17 branch or if 3.17 brought something else along, which
helpt, but AFAICT this is resolved.

Now, however, the GPU doesn't seem to go to the maximum clock anylonger (mclk
goes to max, but I haven't seen the sclk go to max). But I think that's a
different bug/problem.

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

[-- Attachment #1.2: Type: text/html, Size: 2591 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:[~2014-10-08 18:51 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 16:49 [Bug 82201] New: [HAWAII] GPU doesn't reclock, poor 3D performance bugzilla-daemon
2014-08-05 16:54 ` [Bug 82201] " bugzilla-daemon
2014-08-05 16:59 ` bugzilla-daemon
2014-08-05 17:14 ` bugzilla-daemon
2014-08-05 17:32 ` bugzilla-daemon
2014-08-05 18:26 ` bugzilla-daemon
2014-08-05 18:40 ` bugzilla-daemon
2014-08-05 18:55 ` bugzilla-daemon
2014-08-05 19:31 ` bugzilla-daemon
2014-08-05 19:49 ` bugzilla-daemon
2014-08-05 19:51 ` bugzilla-daemon
2014-08-05 19:55 ` bugzilla-daemon
2014-08-05 20:07 ` bugzilla-daemon
2014-08-05 21:08 ` bugzilla-daemon
2014-08-05 21:10 ` bugzilla-daemon
2014-08-05 21:12 ` bugzilla-daemon
2014-08-05 21:15 ` bugzilla-daemon
2014-08-05 21:20 ` bugzilla-daemon
2014-08-05 21:21 ` bugzilla-daemon
2014-08-05 21:23 ` bugzilla-daemon
2014-08-05 21:25 ` bugzilla-daemon
2014-08-05 21:29 ` bugzilla-daemon
2014-08-05 21:32 ` bugzilla-daemon
2014-08-05 22:14 ` bugzilla-daemon
2014-08-06 15:05 ` bugzilla-daemon
2014-08-06 15:16 ` bugzilla-daemon
2014-08-06 15:34 ` bugzilla-daemon
2014-08-09 11:53 ` bugzilla-daemon
2014-08-09 13:55 ` bugzilla-daemon
2014-08-12 12:38 ` bugzilla-daemon
2014-08-12 15:47 ` bugzilla-daemon
2014-08-12 15:58 ` bugzilla-daemon
2014-08-12 19:01 ` bugzilla-daemon
2014-10-08 18:51 ` bugzilla-daemon [this message]
2014-10-12  8:02 ` bugzilla-daemon
2014-10-12  9:45 ` bugzilla-daemon
2014-10-12 12:33 ` bugzilla-daemon
2014-10-12 12:38 ` bugzilla-daemon
2014-10-12 13:14 ` bugzilla-daemon
2014-10-24 22:16 ` bugzilla-daemon
2014-10-24 22:45 ` bugzilla-daemon
2014-10-25 11:10 ` bugzilla-daemon
2014-10-25 11:27 ` bugzilla-daemon
2014-10-25 11:31 ` bugzilla-daemon
2014-10-26 19:00 ` bugzilla-daemon
2014-11-17 17:00 ` bugzilla-daemon
2014-11-17 17:33 ` bugzilla-daemon
2014-12-11 15:57 ` bugzilla-daemon
2014-12-11 16:59 ` bugzilla-daemon
2014-12-11 17:07 ` bugzilla-daemon
2014-12-11 17:36 ` bugzilla-daemon
2014-12-11 18:02 ` bugzilla-daemon
2014-12-11 18:27 ` bugzilla-daemon
2014-12-12  1:30 ` 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-82201-502-xekbiCP95x@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