
| Msg # 1325 of 1332 on ZZLI4424, Thursday 11-05-25, 6:20 |
| From: SALVATORE BONACCORSO |
| To: ALL |
| Subj: Bug#1120058: linux-image-6.16.12+deb14+1 |
05: WR1hp7wSGLCJsQXQ5wuRhOKWw/ 3Y15yWIdCmVGg0+R7b3ZNDuHHf +fUUzsur2YHP4YjfuxE0+N85Av lOC2qbbsuGwXbHfxGbaDWTMBwQe s42mRpoi5gRdXEepTw/AXk34c0J xVIoUIY36o6j9jI0Z8fYzrauxbQ 6MTdYi6NsHKUHo32pYBmc7L2BmX 2adb3069b0e04- XPost: linux.debian.bugs.dist From: carnil@debian.org Control: tags -1 + moreinfo Hi, On Tue, Nov 04, 2025 at 05:05:27PM +0100, J. Neusch??fer wrote: > Package: src:linux > Version: 6.16.12-2 > Severity: normal > X-Debbugs-Cc: debian-amd64@lists.debian.org > User: debian-amd64@lists.debian.org > Usertags: amd64 > > Suspend-to-RAM results in a hang that renders most of userspace > unresponsive on my HP ProBook 445, based on a AMD Ryzen 5 5625U with > Radeon Graphics. Fortunately I was still able to login on a different > TTY and look at htop and dmesg, which showed that systemd-sleep was > stuck in D state. The system was unable to fully enter suspend, or to > resume everything normally. I ran into this issue multiple times with > kernel version 6.16.12, as well as with 6.16.9. > The NVMe storage (PCIe c0a9:0100) may or may not be related to this issue. Can you please provide the full kernel log along so we have the full context? Please try as well the recent uploaded 6.17.7-1 version uploaded to unstable. Can you additionally pin point a earlier version which works which might give a range where you could start bisecting? (though I assume it is not always reproducible). Regards, Salvatore --- SoupGate-Win32 v1.05 * Origin: you cannot sedate... all the things you hate (1:229/2) |
328,098 visits
(c) 1994, bbs@darkrealms.ca