All of 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: Fri, 13 Nov 2015 10:50:55 +0000	[thread overview]
Message-ID: <bug-92936-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 92936
           Summary: Tonga powerplay isssues
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adf.lists@gmail.com

Created attachment 119627
  --> https://bugs.freedesktop.org/attachment.cgi?id=119627&action=edit
dmesg

Testing the amdgpu-powerplay brandh I have several issues.

The first and possibly the cause of others (so for now I won't do separate
bugs) is on boot I see -

Can't find requested voltage id in vdd_dep_on_sclk table!

Testing Games/demos all is good and perf is as expected.

Testing UVD however and perf is way worse than before powerplay.

I see in dmesg -

[ 1818.011402] Failed to send Message.
[ 1818.011407] Failed to send Previous Message.

After doing this I also may no longer get good perf from gamed/demos.

Trying to force high for the uvd test doesn't help and I notice another issue -

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

is auto to start with, if I echo high > it works = GPU gets hotter, but I can't
change it back. If I echo auto > ... then cat it, it will still say high and
GPU remains hot.

Separately when I quit X I may get some new errors in dmesg

Nov 12 11:36:50 ph4 kernel: Failed to send Previous Message.
Nov 12 11:36:50 ph4 kernel: last message repeated 2 times
Nov 12 11:36:50 ph4 kernel: unforce pcie level failed!

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

[-- Attachment #1.2: Type: text/html, Size: 3011 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

             reply	other threads:[~2015-11-13 10:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 10:50 bugzilla-daemon [this message]
2015-11-13 15:53 ` [Bug 92936] Tonga powerplay isssues 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
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@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.