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 92936] Tonga powerplay isssues
Date: Sat, 19 Dec 2015 12:16:01 +0000	[thread overview]
Message-ID: <bug-92936-502-8lUIP0hPmb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92936-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Andy Furniss <adf.lists@gmail.com> ---
Ignoring lockups for now as maybe powerplay/4.5 need something like -

fixes-4.4 commit drm/amdgpu: fix user fence handling

plus I see vaapi threading fixes waiting in mesa.

Testing latest powerplay and the UVD breaks things issue is still present and
there is nothing new in dmesg.

Looking at cat /sys/kernel/debug/dri/64/amdgpu_pm_info what happens is -

Testing opengl initially working though gpu load sometimes looks a bit high
when nothing is happening (clocks still low).

test just UVD (no vo) on auto,  mclk and sclk rise (sclk not 100% though)

After this it seems mclk gets stuck low so running opengl looks like -

 [  mclk  ]: 150 MHz

 [  sclk  ]: 972 MHz

 [GPU load]: 100%

Nothing is logged at this point.

If I now try to force high it fails and I see 

[ 7445.269812] Failed to send Message.
[ 7445.269815] force highest mclk dpm state failed!

Clocks now look like 

 [  mclk  ]: 0 MHz

 [  sclk  ]: 0 MHz

 [GPU load]: 0%

using opengl perf is still low and clocks still say 0 load 100%.

If I use uvd the clocks do go high

 [  mclk  ]: 1375 MHz

 [  sclk  ]: 973 MHz

 [GPU load]: 23%

and they stay high and opengl perf is good again.

cat /sys/class/drm/card0/device/power_dpm_force_performance_level

still says auto.

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

[-- Attachment #1.2: Type: text/html, Size: 2147 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-19 12:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 10:50 [Bug 92936] Tonga powerplay isssues bugzilla-daemon
2015-11-13 15:53 ` bugzilla-daemon
2015-11-13 20:10 ` bugzilla-daemon
2015-11-15 14:29 ` bugzilla-daemon
2015-12-10 12:06 ` bugzilla-daemon
2015-12-12 23:54 ` bugzilla-daemon
2015-12-19 12:16 ` bugzilla-daemon [this message]
2015-12-19 12:41 ` bugzilla-daemon
2016-01-25 21:34 ` bugzilla-daemon
2016-02-05  4:13 ` bugzilla-daemon
2016-02-05 10:41 ` bugzilla-daemon
2016-02-05 14:07 ` bugzilla-daemon
2016-02-05 22:24 ` bugzilla-daemon
2016-02-06 22:26 ` bugzilla-daemon
2016-02-08 22:56 ` bugzilla-daemon
2016-02-08 23:01 ` bugzilla-daemon
2016-02-08 23:01 ` bugzilla-daemon
2016-02-11 18:30 ` bugzilla-daemon
2016-02-11 18:36 ` bugzilla-daemon
2016-02-11 20:07 ` bugzilla-daemon
2016-05-17 10:08 ` bugzilla-daemon
2016-05-17 10:41 ` bugzilla-daemon
2016-05-17 10:42 ` bugzilla-daemon
2016-07-16 14:42 ` bugzilla-daemon
2016-11-07  5:12 ` bugzilla-daemon
2016-11-07 10:17 ` bugzilla-daemon
2018-11-30 17:27 ` 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-92936-502-8lUIP0hPmb@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