From: owner@bugs.debian.org
This is a multi-part message in MIME format...
Your message dated Sun, 21 Sep 2025 08:10:10 +0000
with message-id
and subject line Bug#1114806: fixed in linux 6.16.8-1
has caused the Debian Bug report #1114806,
regarding Regression: Suspend to RAM fails on kernel 6.16.3 (AMDGPU hang)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1114806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114806
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
Received: (at submit) by bugs.debian.org; 10 Sep 2025 06:06:14 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
(2024-03-25) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-8.1 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FOURLA,
FREEMAIL_FROM,GMAIL,HAS_PACKAGE,KHOP_HELO_FCRDNS,NML_ADSP_CUSTOM_MED,
RCVD_IN_PBL,RDNS_DYNAMIC,SPF_SOFTFAIL,SPOOFED_FREEMAIL,SPOOF_GMAIL_MID,
WORD_WITHOUT_VOWELS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 30; hammy, 150; neutral, 287;
spammy,
0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
0.000-+--X-Debbugs-Cc, 0.000-+--forky, 0.000-+--networkmanager,
0.000-+--H*M:reportbug
Return-path:
Received: from 62-178-238-66.cable.dynamic.surfer.at ([62.178.238.66]:52692
helo=[127.0.1.1])
by buxtehude.debian.org with esmtp (Exim 4.96)
(envelope-from )
id 1uwDyA-001CbS-1N
for submit@bugs.debian.org;
Wed, 10 Sep 2025 06:06:14 +0000
Content-Type: multipart/mixed; boundary="==========
=====0126614809158018345=="
MIME-Version: 1.0
From: Marcel Jira
To: Debian Bug Tracking System
Subject: Regression: Suspend to RAM fails on kernel 6.16.3 (AMDGPU hang)
Message-ID: <175748437056.5880.12638445498269870062.reportbug@parasol-
marcel>
X-Mailer: reportbug 13.2.0
Date: Wed, 10 Sep 2025 08:06:10 +0200
Delivered-To: submit@bugs.debian.org
This is a multi-part MIME message sent by reportbug.
--===============0126614809158018345==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: inux-image-6.16.3+deb14-amd64
Version: linux-image-6.16.3+deb14-amd64
Severity: important
Tags: upstream
X-Debbugs-Cc: marcel.jira@gmail.com
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!
Best regards,
Marcel Jira
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.16.3+deb14-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
ANGUAGE=de_AT:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--===============0126614809158018345==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="relevant_suspend.log"
[continued in next message]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|