Control: reassign -1 src:linux 6.16.3-1
Control: tags -1 + moreinfo upstream

Hi Marcel,

On Wed, Sep 10, 2025 at 08:06:10AM +0200, Marcel Jira wrote:
> Package: inux-image-6.16.3+deb14-amd64
> Version: linux-image-6.16.3+deb14-amd64
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: [email protected]
> 
> Dear Maintainer,
> 
> since the upgrade to Linux kernel 6.16.3, suspend to RAM no longer works on my
> system.
> With kernel 6.12.38 (previous version in testing) suspend still works as
> expected, so this is a regression introduced between 6.12 and 6.16.
> 
> ---
> 
> Observed behavior (user perspective):
> - When suspending (on timeout or via power button), the screen turns off as
> expected.
> - Mouse and keyboard LEDs flash a few times, then remain dark (I did not
> observer those flashes on previous kernels, but I am unsure).
> - Screens go dark as expected.
> - The system power button LED stays permanently on (it should normally turn
> off).
> - The system never resumes from suspend.
> - Only a hard power-off (long press on power button) allows restarting the
> machine.
> 
> **Note:** Any unsaved work in RAM is lost due to the required hard reset.
> 
> Expected behavior:
> - System should suspend and resume properly, like under kernel 6.12.38.
> 
> ---
> 
> Log excerpt (from `journalctl -b -1`):
> 
> Sep 10 07:33:02 computer-id kernel: amdgpu 0000:0b:00.0: amdgpu: MODE1 reset
> Sep 10 07:33:02 computer-id kernel: amdgpu 0000:0b:00.0: amdgpu: GPU mode1
> reset
> Sep 10 07:33:02 computer-id kernel: amdgpu 0000:0b:00.0: amdgpu: GPU psp mode1
> reset
> Sep 10 07:33:02 computer-id kernel: amdgpu 0000:0b:00.0: amdgpu: psp reg
> (0x16061) wait timed out, mask: 8000ffff, read: ffffffff exp: 80000000
> 
> 
> This strongly suggests the issue is in the amdgpu driver.
> 
> ---
> 
> Reproducibility:
> - Always, 100% reproducible.
> 
> Hardware:
> CPU: AMD Ryzen 5 3600
> GPU: Radeon RX 5500 XT
> 
> Additional information:
> - systemd was upgraded to 258~rc3-1 at the same time, but suspend works fine
> when booting into kernel 6.12.38 with the new systemd.
> - Logs from the failing suspend attempt (`journalctl -b -1`) are attached in
> full.
> 
> Thank you for your work on the Debian kernel!

Thanks for your report. Ideally please attach the full kernel log to
the bug. Along though I have two questions:

Can you please test the current version in unstable (6.16.5-1), is
the problem solved there?

If not: Can you bisect the upstream changes to isolate the commit
which breaks the behaviour? (Do you need rough instructions on how to
do it?)

Regards,
Salvatore

Reply via email to