From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111913] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors
Date: Mon, 07 Oct 2019 08:17:38 +0000 [thread overview]
Message-ID: <bug-111913-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 5133 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111913
Bug ID: 111913
Summary: AMD Navi10 GPU powerplay issues when using two
DisplayPort connectors
Product: DRI
Version: DRI git
Hardware: All
OS: Linux (All)
Status: NEW
Severity: normal
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: venemo@msn.com
I have a Sapphire AMD RX 5700XT graphics card (the reference design).
When I use DisplayPort-0 and DisplayPort-1 connectors with two Dell U2718Q
monitors, I get the following errors in dmesg.
[ 39.270292] amdgpu: [powerplay] failed send message: TransferTableSmu2Dram
(18) param: 0x00000006 response 0xffffffc2
[ 39.270294] amdgpu: [powerplay] Failed to export SMU metrics table!
[ 41.787785] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh
(14) param: 0x00000080 response 0xffffffc2
[ 44.288882] amdgpu: [powerplay] failed send message: TransferTableSmu2Dram
(18) param: 0x00000006 response 0xffffffc2
[ 44.288883] amdgpu: [powerplay] Failed to export SMU metrics table!
[ 46.822924] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh
(14) param: 0x00000080 response 0xffffffc2
[ 49.237444] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh
(14) param: 0x00000080 response 0xffffffc2
[ 49.353456] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh
(14) param: 0x00000080 response 0xffffffc2
[ 49.353457] amdgpu: [powerplay] Failed to export SMU metrics table!
[ 66.676957] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 69.095868] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 71.634371] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 74.166180] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 76.526822] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 78.804664] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 81.348866] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 83.881667] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 86.335097] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 88.763558] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 91.209310] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 93.740772] amdgpu: [powerplay] failed send message: NumOfDisplays (64)
param: 0x00000002 response 0xffffffc2
[ 128.174369] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xffffffc2
[ 130.597545] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xffffffc2
[ 133.135948] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xffffffc2
[ 135.676398] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xffffffc2
[ 138.213539] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xffffffc2
[ 140.753936] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xffffffc2
[ 143.034004] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xffffffc2
[ 145.313763] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xffffffc2
[ 151.255023] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xffffffc2
[ 153.531678] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xffffffc2
[ 156.054509] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xffffffc2
[ 156.054516] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xfffffffb
[ 156.057923] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xfffffffb
[ 156.057930] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00000000 response 0xfffffffb
[ 156.057932] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xfffffffb
[ 156.057938] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31)
param: 0x00020000 response 0xfffffffb
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6429 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
next reply other threads:[~2019-10-07 8:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 8:17 bugzilla-daemon [this message]
2019-10-07 8:22 ` [Bug 111913] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors bugzilla-daemon
2019-10-07 8:28 ` bugzilla-daemon
2019-10-07 18:46 ` bugzilla-daemon
2019-10-07 19:06 ` bugzilla-daemon
2019-10-07 22:52 ` bugzilla-daemon
2019-10-08 12:02 ` bugzilla-daemon
2019-10-08 13:56 ` bugzilla-daemon
2019-10-08 15:39 ` bugzilla-daemon
2019-10-09 0:24 ` bugzilla-daemon
2019-10-09 18:39 ` bugzilla-daemon
2019-10-13 13:07 ` bugzilla-daemon
2019-10-19 11:24 ` bugzilla-daemon
2019-11-19 9:57 ` 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-111913-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 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.