Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #88221 > unrolled thread

Bug#1108598: amdgpu: incorrectly redrawn screen after resuming from hibernation with Ryzen 5 2400G

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1108598: amdgpu: incorrectly redrawn screen after resuming from hibernation with Ryzen 5 2400G Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2025-07-02 18:20 +0200
    Bug#1108598: amdgpu: incorrectly redrawn screen after resuming from hibernation with Ryzen 5 2400G Ivan Krylov <ikrylov@disroot.org> - 2025-07-04 00:00 +0200

#88221 — Bug#1108598: amdgpu: incorrectly redrawn screen after resuming from hibernation with Ryzen 5 2400G

[Multipart message — attachments visible in raw view] — view raw

tag -1 + moreinfo

Hello,

On Tue, Jul 01, 2025 at 10:21:22AM +0300, Ivan Krylov wrote:
> Package: src:linux
> Version: 6.1.140-1
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: ikrylov@disroot.org
> 
> Dear Maintainer,
> 
> After upgrading from linux-image-6.1.0-34-amd64 to 
> linux-image-6.1.0-37-amd64, the system no longer correctly resumes from 
> hibernation. When the resume process completes, the screen freezes in 
> the VGA text mode (the cursor stops blinking). At this point, 
> Ctrl+Alt+F1 can be used to switch to the text console (and cause the 
> video mode to switch to the native resolution), and after that, Alt+F7 
> can bring me back to X, but in both cases, only the upper-left corner 
> of the screen is drawn. The rest of the screen is filled with the 
> contents of the edges of that area.
> 
> The amdgpu WARN_ON_ONCE is new; the libata WARNING has been there for a 
> long time without any apparent consequences.
> 
> [...]
> [   71.485255] amdgpu 0000:06:00.0: drm_WARN_ON_ONCE(!dev->mode_config.poll_enabled)

I would expect the libata warning to be unrelated. And while we had a
bunch of bug reports about amdgpu in the nearer past, this warning is
new to me.

Can you reliably trigger that problem?

Can you please test a 6.12 kernel (from testing or backports) and/or
6.15 (from experimental)? Depending on if these work better or not, we
need to report upstram or check which patches to backport to 6.1.x (or
convince you to switch to the newer kernel :-)

Best regards
Uwe

[toc] | [next] | [standalone]

#88247

Hello Uwe and thank you for the prompt response!

On Wed, 2 Jul 2025 18:14:27 +0200
Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:

> Can you reliably trigger that problem?

The issue happened to me 4 times out of 4 times I resumed 6.1.0-37 from
hibernation.

> Can you please test a 6.12 kernel (from testing or backports) and/or
> 6.15 (from experimental)?

6.12.32+bpo just resumed without a problem after echo reboot >
/sys/power/disk; echo disk > /sys/power/state. The
drm_WARN_ON_ONCE(!dev->mode_config.poll_enabled) message is gone too.

Bug#1107579 does indeed look similar. Since it seems to work for me, I
wouldn't mind running a kernel from backports as a workaround, but if
you need more information from me to help narrow it down, I can try to
gather it.

-- 
Best regards,
Ivan

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web