All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205979] New: [amdgpu] Vega10 forcing power_dpm_force_performance_level to "high" or "profile_peak", followed by "auto", "low", or "profile_min_mclk" has memory clock stuck at max state
Date: Thu, 26 Dec 2019 18:52:49 +0000	[thread overview]
Message-ID: <bug-205979-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=205979

            Bug ID: 205979
           Summary: [amdgpu] Vega10 forcing
                    power_dpm_force_performance_level to "high" or
                    "profile_peak", followed by "auto", "low", or
                    "profile_min_mclk" has memory clock stuck at max state
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.4.6-gentoo
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: stefanspr94@gmail.com
        Regression: No

Memory can only be brought back to lower clocks when setting
power_dpm_force_performance_level to "manual" and forcing a lower socclk state
eg. "2" in pp_dpm_socclk or by rebooting.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2019-12-26 18:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-205979-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.