https://bugs.freedesktop.org/show_bug.cgi?id=107518

--- Comment #1 from Shawn Anastasio shawnanastasio@yahoo.com --- Created attachment 141003 --> https://bugs.freedesktop.org/attachment.cgi?id=141003&action=edit dmesg for 4.18.0-rc8+

https://bugs.freedesktop.org/show_bug.cgi?id=107518

--- Comment #3 from Alex Deucher alexdeucher@gmail.com --- (In reply to Shawn Anastasio from comment #2)

Upon further testing, the issue seems to go away when the firmware is removed from petitboot, preventing it from initializing the card before the host OS. This indicates that it may have something to do with the GPU being initialized twice.

The hw requires a special reset before it can be initialized again. This is handled in driver for things like hibernate (S4) support.

https://bugs.freedesktop.org/show_bug.cgi?id=107518

--- Comment #5 from Alex Deucher alexdeucher@gmail.com --- (In reply to Shawn Anastasio from comment #4)

Does the driver do the reset on a kexec reboot? If so, it seems insufficient to mitigate this issue.

Probably not. I'm not that familiar with kexec unfortunately.

https://bugs.freedesktop.org/show_bug.cgi?id=107518

--- Comment #7 from Alex Deucher alexdeucher@gmail.com --- amdgpu_pmops_freeze() calls amdgpu_device_suspend() which calls amdgpu_asic_reset() at the end. amdgpu_asic_reset() is a macro which calls an asic specific callback to reset the GPU. vi_asic_reset() in vi.c is the callback for polaris and other VI family parts.

https://bugs.freedesktop.org/show_bug.cgi?id=107518

--- Comment #9 from Timothy Pearson tpearson@raptorengineering.com --- (In reply to Timothy Pearson from comment #8)

Would it make sense to call amdgpu_asic_reset() as part of module load to ensure that the GPU is in a known good state?

This didn't fix the problem, but I did note that rmmod / modprobing the amdgpu module from the host is a valid workaround. Something must happen on rmmod-based teardown aside from amdgpu_asic_reset().

https://bugs.freedesktop.org/show_bug.cgi?id=107518

--- Comment #11 from Luigi Laurini moonlght@tiscali.it --- Same bug present in amd64 architecture under kvm guest with RX 480 passed through. The first time i boot the guest the performance are ok, but if i reboot the guest without rebooting the host, the messages appears.

Tried the patch

https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-next&...

The message are gone but the performance problem is still present.

the problem affects the memory/gpu clocking:

First boot of the guest:

cat /sys/kernel/debug/dri/0/amdgpu_pm_info Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off

GFX Clocks and Power: 1750 MHz (MCLK) 330 MHz (SCLK) 300 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1000 mV (VDDGFX) 19.127 W (average GPU)

GPU Temperature: 56 C GPU Load: 0 %

UVD: Disabled

VCE: Disabled

if i reboot the guest:

cat /sys/kernel/debug/dri/0/amdgpu_pm_info Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off

GFX Clocks and Power: 300 MHz (MCLK) 300 MHz (SCLK) 300 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 800 mV (VDDGFX) 7.162 W (average GPU)

GPU Temperature: 42 C GPU Load: 0 %

UVD: Disabled

VCE: Disabled

https://bugs.freedesktop.org/show_bug.cgi?id=107518

--- Comment #13 from Timothy Pearson tpearson@raptorengineering.com --- The patch originally at https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-next&... is no longer available:

Bad commit reference: 8242308cc3c4419832126ab78ca409ce7110ab33

Is an equivalent now in mainline? I'd like to try it out on one of our POWER9 boxes.

Thanks!

https://bugs.freedesktop.org/show_bug.cgi?id=107518

Martin Peres martin.peres@free.fr changed:

What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED

--- Comment #15 from Martin Peres martin.peres@free.fr --- -- 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/474.