From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100443] DMESG: [powerplay] Can't find requested voltage id in vdd_dep_on_sclk table!
Date: Fri, 13 Oct 2017 11:49:51 +0000 [thread overview]
Message-ID: <bug-100443-502-6yzIvcntrG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100443-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100443
--- Comment #35 from Devin Prince <semperverus@gmail.com> ---
Upon further investigation, I would like to ammend my previous comment.
Setting amdgpu.dpm=0 will allow you to bypass those errors by disabling dpm
altogether, but the consequence is that the fans will stop spinning almost
entirely (slow or no fan speeds when they should be ramping up).
Instead, set:
amdgpu.ppfeaturemask=1
which enables the card to broadcast all of its power states properly. With this
enabled, all the errors mentioned in this thread vanished from my system, and
in addition, the hwmon features actually showed up under
/sys/class/drm/card0/device/hwmon/hwmon0/ and I can even echo speeds to pwm1.
I'm unsure if this has any adverse effects on anything, but if it does not,
perhaps ppfeaturemask should be set to default enabled in the amdgpu driver.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1833 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
next prev parent reply other threads:[~2017-10-13 11:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 8:04 [Bug 100443] DMESG: [powerplay] Can't find requested voltage id in vdd_dep_on_sclk table! bugzilla-daemon
2017-03-29 20:17 ` bugzilla-daemon
2017-03-29 20:48 ` bugzilla-daemon
2017-04-03 14:34 ` bugzilla-daemon
2017-04-13 10:32 ` bugzilla-daemon
2017-04-13 10:32 ` bugzilla-daemon
2017-04-13 10:33 ` bugzilla-daemon
2017-05-07 6:17 ` bugzilla-daemon
2017-05-16 8:37 ` bugzilla-daemon
2017-05-16 10:08 ` bugzilla-daemon
2017-07-09 9:56 ` bugzilla-daemon
2017-07-09 12:41 ` bugzilla-daemon
2017-07-09 13:03 ` bugzilla-daemon
2017-07-10 19:02 ` bugzilla-daemon
2017-08-05 22:27 ` bugzilla-daemon
2017-08-05 22:28 ` bugzilla-daemon
2017-08-05 23:08 ` bugzilla-daemon
2017-08-05 23:16 ` bugzilla-daemon
2017-08-06 15:08 ` bugzilla-daemon
2017-08-06 15:12 ` bugzilla-daemon
2017-08-06 21:08 ` bugzilla-daemon
2017-08-06 21:29 ` bugzilla-daemon
2017-08-06 22:26 ` bugzilla-daemon
2017-08-06 23:10 ` bugzilla-daemon
2017-08-07 11:08 ` bugzilla-daemon
2017-08-07 11:14 ` bugzilla-daemon
2017-08-07 11:22 ` bugzilla-daemon
2017-08-07 11:43 ` bugzilla-daemon
2017-08-07 12:06 ` bugzilla-daemon
2017-08-07 15:22 ` bugzilla-daemon
2017-08-11 15:12 ` bugzilla-daemon
2017-09-16 0:22 ` bugzilla-daemon
2017-09-26 8:58 ` bugzilla-daemon
2017-09-28 18:01 ` bugzilla-daemon
2017-10-13 7:00 ` bugzilla-daemon
2017-10-13 11:49 ` bugzilla-daemon [this message]
2017-10-16 14:05 ` bugzilla-daemon
2017-11-28 20:37 ` bugzilla-daemon
2017-12-15 8:08 ` bugzilla-daemon
2018-09-20 4:17 ` bugzilla-daemon
2018-09-20 4: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-100443-502-6yzIvcntrG@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;
as well as URLs for NNTP newsgroup(s).