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 106428] reported VDDGFX GPU voltage jumps above set limits in pp_od_clk_voltage when UVD is used for VAAPI/VDPAU
Date: Mon, 07 May 2018 13:12:27 +0000	[thread overview]
Message-ID: <bug-106428-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 106428
           Summary: reported VDDGFX GPU voltage jumps above set limits in
                    pp_od_clk_voltage when UVD is used for VAAPI/VDPAU
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: tempel.julian@gmail.com

I adjusted my pstates in "/sys/class/drm/card0/device/pp_od_clk_voltage" that
the GPU voltage should never be above 900 mV:

(...)
5:       1126Mhz        880 mV
6:       1180Mhz        890 mV
7:       1209Mhz        900 mV

And in normal 3D applications "watch -n 0.5  cat
/sys/kernel/debug/dri/0/amdgpu_pm_info" accordingly never reports more than 900
mV for VDDGFX.

But when I play a video in mpv with VAAPI/VDPAU, reported VDDGFX often jumps to
1100 mV, which clearly is undesired behavior. It sticks again to normal 900 mV
as soon as I disable hardware decoding.

Now the question is, if the reported voltage is correct (then adjusting
pp_od_clk_voltage has a bug) or if the real voltage is just reported wrong
(than information in amdgpu_pm_info would be wrong).

Happens with both 4.17rc2 and drm-next-4.18-wip.
GPU is RX 560.

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

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

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

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

             reply	other threads:[~2018-05-07 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 13:12 bugzilla-daemon [this message]
2018-05-10 13:40 ` [Bug 106428] reported VDDGFX GPU voltage jumps above set limits in pp_od_clk_voltage when UVD is used for VAAPI/VDPAU bugzilla-daemon
2018-11-29 10:58 ` 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-106428-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox