clbr / radeontop

GNU General Public License v3.0
810 stars 72 forks source link

radeontop spams journal log with warning messages #122

Open CodeMonkey80s opened 3 years ago

CodeMonkey80s commented 3 years ago

Hardware info:

$ sudo lshw -C display
  *-display                 
       description: VGA compatible controller
       product: Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:03:00.0
       version: c1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:174 memory:a0000000-afffffff memory:b0000000-b01fffff ioport:4000(size=256) memory:99100000-991fffff memory:c0000-dffff

$ inxi -Gx
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Tul driver: amdgpu 
           v: kernel bus ID: 03:00.0 
           Display: server: X.Org 1.20.11 driver: loaded: modesetting resolution: 3440x1440~144Hz 
           OpenGL: renderer: AMD Radeon RX 6800 XT (SIENNA_CICHLID DRM 3.41.0 5.13.11-051311-lowlatency LLVM 12.0.1) 
           v: 4.6 Mesa 21.3.0-devel (git-c94ff7d 2021-08-18 hirsute-oibaf-ppa) direct render: Yes

Software Info:

$ sudo apt show radeontop
Package: radeontop
Version: 1.3-1

$ lsb_release -r
Release:    21.04

Messages in the journal log:

Aug 18 18:37:55 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable gfxoff!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable gfxoff!
Aug 18 18:38:06 dagon kernel: filter_write: 47 callbacks suppressed
Aug 18 18:38:06 dagon kernel: msr: Write to unrecognized MSR 0x38f by i7z (pid: 30950).
Aug 18 18:38:06 dagon kernel: msr: See https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/about for details.
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable gfxoff!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable gfxoff!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable gfxoff!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:06 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable gfxoff!
Aug 18 18:38:07 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Aug 18 18:38:07 dagon kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable gfxoff!

Once I kill radeontop these messages stop appearing in the log.

PS: I tried searching what actually these messages mean but I failed. So I have no idea if they are important or not...

NOTE: Let's put this one onhold as I don't see these messages anymore after a reboot. I will do some investigation and get back here.

clbr commented 3 years ago

Kinda looks like a bug in the amdgpu driver rather.