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 74250] [HAWAII][DPM] New Version 3.1 for ASIC_ProfilingInfo / ci_upload_dpm_level_enable_mask failed
Date: Fri, 01 Aug 2014 15:48:23 +0000	[thread overview]
Message-ID: <bug-74250-502-kiPkNeKRLv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-74250-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Luzipher <luziphermcleod@yahoo.ie> ---
(In reply to comment #4)
> Please try the attached patches.

Yay, those help ! Thanks a lot, Alex ! :-)
With all three patches (attachements #93015, #103772, #103773) I get working
DPM and none of the error messages above.
I used the drm-next-3.17-wip kernel from yesterday with the patches applied
manually (noticed you committed them just after I started the build). I think
you didn't commit #93015 ?

I also tried without attachment #93015, but I can't really explain the results.
I expected to see the "*ERROR* Unknown table version 3, 1" message, but it
didn't show up. Still dpm didn't work and I did get the "*ERROR*
ci_upload_dpm_level_enable_mask failed" message.

DPM also seems to work quite correcty, the card goes up to over 1GHz (1040MHz
should be max for my card) on sclk, mclk always stays the same (but is
different than without dpm):
# cat /sys/kernel/debug/dri/0/radeon_pm_info
power level avg    sclk: 100120 mclk: 130000

Without the patches, I always got:
power level avg    sclk: 30000 mclk: 15000

Half-Life 2 now runs more or less constantly at 60fps with hig details and 8x
MSAA :-) Metro Last Light is only at 20-30fps, but that's still great. What I
don't really understand is that Metro didn't feel much slower when dpm didn't
work (HL2 certainly did).


I guess sclk stands for "shader clock" and mclk is for "memory clock" ? On
Windows I believe I also have different memory clocks between the desktop and
in games - is memory clocking not dynamic yet ?

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

[-- Attachment #1.2: Type: text/html, Size: 2914 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-08-01 15:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 22:48 [Bug 74250] New: [HAWAII][DPM] New Version 3.1 for ASIC_ProfilingInfo / ci_upload_dpm_level_enable_mask failed bugzilla-daemon
2014-01-30 22:55 ` [Bug 74250] " bugzilla-daemon
2014-04-22 22:43 ` bugzilla-daemon
2014-07-29 22:43 ` bugzilla-daemon
2014-07-31 22:17 ` bugzilla-daemon
2014-07-31 22:17 ` bugzilla-daemon
2014-08-01 15:48 ` bugzilla-daemon [this message]
2014-08-01 16:46 ` bugzilla-daemon
2014-08-02 15:21 ` bugzilla-daemon
2014-08-03 19:41 ` bugzilla-daemon
2014-08-03 19:43 ` bugzilla-daemon
2014-08-03 19:43 ` bugzilla-daemon
2014-08-03 19:44 ` bugzilla-daemon
2014-08-03 19:45 ` bugzilla-daemon
2014-08-04 19:52 ` 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-74250-502-kiPkNeKRLv@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