On Tuesday, 8 February 2022 08:11:46 CET Salvatore Bonaccorso wrote:
> Does this help?
It did:
$ git bisect good
3c196f05666610912645c7c5d9107706003f67c3 is the first bad commit
commit 3c196f05666610912645c7c5d9107706003f67c3
Author: Alex Deucher <alexander.deuc...@amd.com>
Date: Fri Nov 12 11:25:30 2021 -0500
drm/amdgpu: always reset the asic in suspend (v2)
[ Upstream commit daf8de0874ab5b74b38a38726fdd3d07ef98a7ee ]
If the platform suspend happens to fail and the power rail
is not turned off, the GPU will be in an unknown state on
resume, so reset the asic so that it will be in a known
good state on resume even if the platform suspend failed.
v2: handle s0ix
Acked-by: Luben Tuikov <luben.tui...@amd.com>
Acked-by: Evan Quan <evan.q...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Signed-off-by: Sasha Levin <sas...@kernel.org>
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
Note that the amdgpu error message and kernel warnings are always shown in
kernel logs. They are not related to the failing suspend.
Now I need to investigate whether the failed suspend or kernel message are
related to my external usb device (a usb-c hub with LAN and HDMI output).
All the best
