All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111762] RX 5700 XT Navi - amdgpu.ppfeaturemask=0xffffffff causes stuttering and does not unlock clock/voltage/power controls
Date: Sun, 20 Oct 2019 11:26:38 +0000	[thread overview]
Message-ID: <bug-111762-502-RVu6eDREcR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111762-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from tempel.julian@gmail.com ---
Still happens with current 5.5-wip/drm-next kernels.
I don't know if it is supposed to be implemented, but there seems to be some
bug apart from that:
Just reading sysfs entries at "/sys/class/drm/card0/device/" makes the parsing
program freeze, e.g. filebrowser (also if started as root).

Anyhow, "# cat /sys/class/drm/card0/device/pp_od_clk_voltage" returns nothing.

Could there be an update on this? Not being able to overclock/undervolt almost
4 months after Navi release is a huge disappointment.

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

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

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

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

  reply	other threads:[~2019-10-20 11:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22  9:54 [Bug 111762] RX 5700 XT Navi - amdgpu.ppfeaturemask=0xffffffff causes stuttering and does not unlock clock/voltage/power controls bugzilla-daemon
2019-10-20 11:26 ` bugzilla-daemon [this message]
2019-10-21  1:42 ` bugzilla-daemon
2019-10-21 17:33 ` bugzilla-daemon
2019-10-21 17:38 ` bugzilla-daemon
2019-10-24 13:31 ` bugzilla-daemon
2019-10-25 15:36 ` bugzilla-daemon
2019-11-07 18:47 ` bugzilla-daemon
2019-11-07 18:48 ` bugzilla-daemon
2019-11-07 18:50 ` bugzilla-daemon
2019-11-08 19:25 ` bugzilla-daemon
2019-11-08 19:39 ` bugzilla-daemon
2019-11-08 19:46 ` bugzilla-daemon
2019-11-08 20:13 ` bugzilla-daemon
2019-11-08 21:00 ` bugzilla-daemon
2019-11-08 21:02 ` bugzilla-daemon
2019-11-08 21:02 ` bugzilla-daemon
2019-11-19  9: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-111762-502-RVu6eDREcR@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.