| Bug ID | 111555 |
|---|---|
| Summary | [amdgpu/Navi] [powerplay] Failed to send message errors |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | not set |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | shtetldik@gmail.com |
I get periodic errors like this in dmesg, which coincides with=
intermittent
system stalls:
[Wed Sep 4 00:43:43 2019] amdgpu: [powerplay] Failed to send message 0=
x12,
response 0xfffffffb param 0x6
[Wed Sep 4 00:43:43 2019] amdgpu: [powerplay] Failed to export SMU met=
rics
table!
[Wed Sep 4 00:44:53 2019] amdgpu: [powerplay] Failed to send message 0=
xe,
response 0xfffffffb, param 0x80
[Wed Sep 4 00:44:53 2019] amdgpu: [powerplay] Failed to send message 0=
xf,
response 0xfffffffb, param 0xa90000
[Wed Sep 4 00:45:30 2019] amdgpu: [powerplay] Failed to send message 0=
x12,
response 0xfffffffb, param 0x6
[Wed Sep 4 00:45:35 2019] amdgpu: [powerplay] Failed to send message 0=
x12,
response 0xfffffffb param 0x6
[Wed Sep 4 00:45:35 2019] amdgpu: [powerplay] Failed to export SMU met=
rics
table!
I'm running kernel 5.3-rc7
GPU: Sapphire Pulse RX 5700XT (Navi 10) with firmware from=20
http=
s://people.freedesktop.org/~agd5f/radeon_ucode/navi10/
Distro: Debian testing / KDE.
I noticed, that it starts happening often when I'm using ksysguard, which
queries lm-sensors for amdgpu temperature and fan speed.
These errors also happen when using radeon-profile to control = the fan speed: [ 3099.422315] amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb param 0x80 [ 3099.422318] amdgpu: [powerplay] Failed to export SMU metrics table! [ 3145.423048] amdgpu: [powerplay] Failed to send message 0x12, response 0xfffffffb param 0x6 [ 3145.423051] amdgpu: [powerplay] Failed to export SMU metrics table! [ 3145.423076] amdgpu: [powerplay] Failed to send message 0x12, response 0xfffffffb, param 0x6 [ 3149.423073] amdgpu: [powerplay] Failed to send message 0x12, response 0xfffffffb param 0x6 [ 3149.423076] amdgpu: [powerplay] Failed to export SMU metrics table! [ 3200.422744] amdgpu: [powerplay] Failed to send message 0xf, response 0xfffffffb, param 0xa90000 [ 3200.422846] amdgpu: [powerplay] Failed to send message 0x12, response 0xfffffffb param 0x6 [ 3200.422850] amdgpu: [powerplay] Failed to export SMU metrics table! [ 3234.422189] amdgpu: [powerplay] Failed to send message 0xf, response 0xfffffffb, param 0xa90000
Related: https://github.com/marazmista/radeon-profile/issues/157<= /pre>
Are you running a monitor at 75hz? I can only trigger the bug when setting 74-76hz with amd-staging-drm-next, = and although I haven't tested in a while, I suspect the same applies with 5.3-r= cX (and drm-next-5.4). Here's the output after setting 75hz, on amd-staging-drm-next: [ 7937.682003] amdgpu: [powerplay] failed send message: TransferTableSmu2Dr= am (18) param: 0x00000006 response 0xffffffc2 [ 7937.682004] amdgpu: [powerplay] Failed to export SMU metrics table! [ 7938.087356] amdgpu: [powerplay] failed send message: NumOfDisplays (64)= =20=20=20=20=20 param: 0x00000001 response 0xffffffc2 [ 7940.224391] amdgpu: [powerplay] failed send message: TransferTableSmu2Dr= am (18) param: 0x00000006 response 0xffffffc2 [ 7940.224392] amdgpu: [powerplay] Failed to export SMU metrics table! [ 7942.362952] amdgpu: [powerplay] failed send message: SetDriverDramAddrHi= gh (14) param: 0x00000080 response 0xffffffc2 [ 7944.510060] amdgpu: [powerplay] failed send message: SetDriverDramAddrHi= gh (14) param: 0x00000080 response 0xffffffc2 [ 7944.510061] amdgpu: [powerplay] Failed to export SMU metrics table! [ 7945.269921] amdgpu: [powerplay] failed send message: NumOfDisplays (64)= =20=20=20=20=20 param: 0x00000001 response 0xffffffc2 [ 7946.652777] amdgpu: [powerplay] failed send message: SetDriverDramAddrHi= gh (14) param: 0x00000080 response 0xffffffc2 [ 7947.411808] amdgpu: [powerplay] failed send message: NumOfDisplays (64)= =20=20=20=20=20 param: 0x00000001 response 0xffffffc2 [ 7948.786413] amdgpu: [powerplay] failed send message: SetDriverDramAddrHi= gh (14) param: 0x00000080 response 0xffffffc2 [ 7948.786414] amdgpu: [powerplay] Failed to export SMU metrics table! [ 7950.918131] amdgpu: [powerplay] failed send message: SetDriverDramAddrHi= gh (14) param: 0x00000080 response 0xffffffc2 [ 7953.076247] amdgpu: [powerplay] failed send message: SetDriverDramAddrHi= gh (14) param: 0x00000080 response 0xffffffc2 [ 7953.076250] amdgpu: [powerplay] Failed to export SMU metrics table!
(In reply to Andrew Sheldon from comment #3) > Are you running a monitor at 75hz? > No, 60 Hz which is my monitor's native refresh rate.
I can confirm this happens when I use a dual-monitor setup. I = have two 1440p@144 Hz screens and these messages happen when I boot with both sc= reens, or look at the gpu temperature through the sensor command, with both screens active. With only one screen active, I cannot reproduce the bug.
Just for the reference, my connection is DisplayPort 1.2.
I ran into this issue when messing around with my BIOS setting= s. Not sure if helpful but when I had the option Decode Above 4G (64bit adressing on PCI b= us?) on my Gigabyte Aorus B450 I experienced the same issue. After turning that option back off everything is working again.
I don't get these errors anymore when using radeon-profile wit= h kernel 5.4-rc6. But with ksysguard, Failed to export SMU metrics table! message is still occurring, though it's not causing any stalls or hangs now.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/900.