#1104327 firmware-amd-graphics: after laptop resume, AMD graphics jsut show large patterns on all terminals

#1104327#5
Date:
2025-04-29 04:27:58 UTC
From:
To:
starting the laptop, the behavior is normal.
sending the laptop to sleep and resume, no terminal is usable.
Instead large pattern are shown. On Wayland terminal two rows of rects, the
mouse cursor is a large square.
On text console are vertical or diagonal rows of dots shown

#1104327#10
Date:
2025-04-29 10:49:48 UTC
From:
To:
with kernel #1 SMP PREEMPT_DYNAMIC Debian 6.12.22-1 everything seems to
behave normal

#1104327#21
Date:
2025-05-07 10:34:26 UTC
From:
To:
Hello Dietmar,

Is this reliably reprodicible?

Can you please followup with a kernel log of the broken system?

Probably the easiest and most helpful way to do that is to use

	reportbug linux-image-6.12.25-amd64

and then select 1104327 and then press "x" for "Provide extra
information." and then add the output of `dmesg` (as attachment or
inline whatever works for you).

Best regards
Uwe

#1104327#28
Date:
2025-05-07 20:23:56 UTC
From:
To:

#1104327#33
Date:
2025-05-07 20:27:37 UTC
From:
To:
Hi Uwe,

how to send you a kernel log from last boot? after resume and seeing the
niche patterns :-) I can't interact with the system.

current observation is, the bug exists in 6.12.25 and 6.12.27, but not
in 6.12.22

Dietmar

#1104327#38
Date:
2025-05-08 06:02:44 UTC
From:
To:
Hello Dietmar,

I somehow expected that network access is still working and you could
ssh in from another machine. Did you consider that?

Thanks
Uwe

#1104327#43
Date:
2025-05-09 18:46:39 UTC
From:
To:

#1104327#48
Date:
2025-05-19 17:00:03 UTC
From:
To:
I installed this morning the 6.12.29 Kernel, the bug is still present.


Kindly

Dietmar

#1104327#55
Date:
2025-05-21 04:05:24 UTC
From:
To:
Same with kernel 6.14 from experimental
#1104327#60
Date:
2025-05-22 06:33:00 UTC
From:
To:
Resume from hibernation work as normal with kernel 6.12.29
#1104327#65
Date:
2025-05-24 09:20:26 UTC
From:
To:
hi Diedmar,

Thanks for provinding the full boot logs. So this looks like an issue
which should be reported to amdgpu upstream. Since they might have
some questions back, can you please fill a bugreport upstream
providing the information in a new issue on
https://gitlab.freedesktop.org/drm/amd/-/issues ?

Could you then please report back the issue reference so we can track
it here for downstream?

Regards,
Salvatore