Getting the following syslog spam every 1 seconds with RX 5700 card installed in system:
kernel: amdgpu: [powerplay] Failed to send message 0x0, response 0xfffffffb
kernel: amdgpu: [powerplay] Attempt to get current RPM from SMC Failed!
kernel: amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, param 0x80
AMDGPU installed from provided driver .deb packages with installer script. dkms build finished without errors. Hardware and OS specs are as follows:
mobo: Gigabyte X399 Designare EX with latest bios (F12g)
cpu: Threadripper 2920X
ram: 8x 16GB Samsung ECC
gpu: MSI RX 5700
os: Ubuntu 18.04.2 LTS
kernel: 5.0.0-16-generic (hwe-edge stack)
It appears that the driver doesn't provide any facilities for limiting log messages, which would be very useful in a situation like this.
Also, running 'sensors' gives the following error:
$ sudo sensors
[...snip...]
amdgpu-pci-0b00
Adapter: PCI adapter
vddgfx: +0.78 V
ERROR: Can't get value of subfeature fan1_input: I/O error
fan1: N/A (min = 0 RPM, max = 4950 RPM)
edge: N/A (crit = +80.0°C, hyst = +0.0°C)
(emerg = +80.0°C)
junction: N/A (crit = +80.0°C, hyst = +0.0°C)
(emerg = +80.0°C)
mem: N/A (crit = +80.0°C, hyst = +0.0°C)
(emerg = +80.0°C)
power1: 30.00 W (cap = 150.00 W)[...snip...]
Same problem with my RX 5700 XT and Ryzen 9 (Motherboard is ASUS ROG Strix X570-E). Updating to amdgpu-pro-19.30-855429-ubuntu-18.04 did NOT fix the problem.
Same issue here.
MB: ASUS TUF B450M-PLUS GAMING
CPU: AMD Ryzen 5 2600
GPU: PowerColor Red Devil Radeon RX 5700 XT (AXRX 5700XT 8GBD6-3DHE/OC)
Driver version: AMDGPU-Pro 19.30-855429
Kernel: 5.0.0-31-generic
OS: Ubuntu 18.04.1
That sounds really annoying and a bit familiar. I think I had something like that a long time ago with AMD drivers. I have two thoughts; not sure if you will find them helpful.
1) syslog is not strictly needed; you could remove it. I've been running without it for a while and it's been fine on my personal desktop system. Before you do that, check journalctl to see if you aren't getting duplicates in there, too. The journal may even de-duplicate that sort of thing efficiently, so the impact may not even be noticeable. But, syslog may be flushing buffers to disk frequently at that rate, and you probably are noticing it.
2) rsyslog (and syslog, I think) has a way to drop messages based on regex match...sorry, I don't have notes about how to do this, but I've done it before, so I know it works.