Bug 107593

Summary: spam in dmesg about "SADs count" since recent Radeon RX550 install using amdgpu driver
Product: DRI Reporter: Fermulator <freedesktop-bugs>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: harry.wentland, sunpeng.li
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg output from past few days with SADs count spam
none
drm spam from other system, real data coming none

Description Fermulator 2018-08-16 16:17:17 UTC
Created attachment 141140 [details]
dmesg output from past few days with SADs count spam

this message is being written in dmesg output quite frequently
```
[drm] SADs count is: -524, don't need to read it
```
Comment 1 Fermulator 2018-08-16 16:18:26 UTC
$ uname -a
Linux (SNIP) 4.17.12-100.fc27.x86_64 #1 SMP Fri Aug 3 15:00:33 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/fedora-release
Fedora release 27 (Twenty Seven)

$ rpm -qa | egrep "amdgpu"
xorg-x11-drv-amdgpu-18.0.1-1.fc27.x86_64
Comment 2 Fermulator 2018-08-16 16:19:10 UTC
$ lshw -C video
WARNING: you should run this program as super-user.
  *-display                 
       description: VGA compatible controller
       product: Lexa PRO [Radeon RX 550/550X]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:03:00.0
       version: c7
       width: 64 bits
       clock: 33MHz
       capabilities: vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:30 memory:e0000000-efffffff memory:f0000000-f01fffff ioport:e000(size=256) memory:fbe00000-fbe3ffff memory:c0000-dffff

$ lspci | grep -i amd
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon RX 550/550X] (rev c7)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0
Comment 3 Fermulator 2018-08-16 16:29:25 UTC
Of note, I just compared to a DIFFERENT system I own, also running amdgpu ... the spam is there too but dumping real information (still, spam is undesired)

```
[Wed Aug 15 23:21:34 2018] [drm] {1920x1080, 2200x1125@148500Khz}
```

$ sudo lshw -C video
  *-display                 
       description: VGA compatible controller
       product: Ellesmere [Radeon RX 470/480]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:07:00.0
       version: ef
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:63 memory:c0000000-cfffffff memory:d0000000-d01fffff ioport:c000(size=256) memory:fe600000-fe63ffff memory:c0000-dffff


$ cat /etc/issue
Ubuntu 18.04.1 LTS \n \l

$ uname -a
Linux SNIP 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

ii  libdrm-amdgpu1:amd64                                             2.4.91-2                                     amd64        Userspace interface to amdgpu-specific kernel DRM services -- runtime
ii  libdrm-amdgpu1:i386                                              2.4.91-2                                     i386         Userspace interface to amdgpu-specific kernel DRM services -- runtime
ii  xserver-xorg-video-amdgpu                                        18.0.1-1                                     amd64        X.Org X server -- AMDGPU display driver
Comment 4 Fermulator 2018-08-16 16:30:10 UTC
Created attachment 141141 [details]
drm spam from other system, real data coming
Comment 5 Michel Dänzer 2018-08-16 16:32:10 UTC
(In reply to Fermulator from comment #3)
> ```
> [Wed Aug 15 23:21:34 2018] [drm] {1920x1080, 2200x1125@148500Khz}
> ```

These particular messages are fixed in current kernels.
Comment 6 Fermulator 2018-08-24 13:25:34 UTC
"current kernels", more specifically?
(Fedora runs pretty bleeding edge kernel-wise)

If we have a "fix in kernel version X", and a different bug report to duplicate against, we can close then then?
Comment 7 Michel Dänzer 2018-08-24 14:06:51 UTC
(In reply to Fermulator from comment #6)
> "current kernels", more specifically?

4.16 or newer.

> If we have a "fix in kernel version X", and a different bug report to
> duplicate against, we can close then then?

I was only referring to the

  [drm] {1920x1080, 2200x1125@148500Khz}

messages. The "SADs count" messages are still there.
Comment 8 Fermulator 2018-08-27 15:30:26 UTC
(understood) - so the SADs count is a bug to be fixed
(the comparison I provided against legit data is N/A here and anyway is fixed in newer kernel versions)
Comment 9 Martin Peres 2019-11-19 08:47:08 UTC
-- 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/479.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.