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: Wed, 29 Mar 2017 08:04:30 +0000 [thread overview]
Message-ID: <bug-100443-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1735 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100443
Bug ID: 100443
Summary: DMESG: [powerplay] Can't find requested voltage id in
vdd_dep_on_sclk table!
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: freedesktop@lanig.email
Created attachment 130529
--> https://bugs.freedesktop.org/attachment.cgi?id=130529&action=edit
DMESG excerpt
System:
Ubuntu 17.04 + Kernel 4.11 RC4 + Padoka PPA
AMD Ryzen 7 1700X
ASRock AB350 Pro4 Bios v1.40 (because 2.20 breaks ECC)
XfX RX 480 RS
2x16GiB Crucial CT2K16G4XFD824A ECC Kit
After installing my new motherboard and CPU I just went through the system
messages to see how well it's supported or if there are some issues to be
sorted out.
Unfortunately it looks like there are issues with AMDGPU, at the initialization
there are really massive warnings and errors.
It starts with these several times:
[ 1.482118] AMD-Vi: Event logged [
[ 1.482118] IO_PAGE_FAULT device=0c:00.0 domain=0x0003
address=0x000000f4001e6a00 flags=0x0010]
And ends in telling me that something is wrong with the powerplay:
[ 1.526878] amdgpu: [powerplay] [AVFS] Something is broken. See log!
[ 1.528706] amdgpu: [powerplay] Can't find requested voltage id in
vdd_dep_on_sclk table!
This report has been separated from this one:
https://bugs.freedesktop.org/show_bug.cgi?id=100437
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3313 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 reply other threads:[~2017-03-29 8:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 8:04 bugzilla-daemon [this message]
2017-03-29 20:17 ` [Bug 100443] DMESG: [powerplay] Can't find requested voltage id in vdd_dep_on_sclk table! 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
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@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).