Bug#1137142: linux-image-amd64: Screen goes black dozen of seconds after resume from suspend state on ThinkPad T16 2023
Fonzie Huang <[email protected]> Wed, 20 May 2026 12:05:14 +0800
| Newsgroups | gmane.linux.debian.ports.amd64 |
|---|---|
| Message-ID | <177924991429.143759.8847376726725320482.reportbug__11017.5663184904$1779250051$gmane$org@Laptop3> |
Package: linux-image-amd64 Version: 6.12.88-1 Severity: important Tags: upstream X-Debbugs-Cc: [email protected], [email protected] User: [email protected] Usertags: amd64 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After upgrading from linux-image-6.12.85+deb13-amd64 to linux-image-6.12.85+deb13-amd64 for fix of CVE-2026-31431, and to linux-image-6.12.88+deb13-amd64 for fix of later CVE(s), my ThinkPad T16 AMD 2023 frequently goes black after resuming from suspend state. The problem can be reproduced when I was running linux-image-6.12.85+deb13-amd64 or linux-image-6.12.88+deb13-amd64. Call Trace from journalctl --dmesg that keep appearing during the problematic period: <TASK> __schedule+0x505/0xc00 schedule+0x27/0xf0 schedule_timeout+0x12f/0x160 wait_for_completion+0x8a/0x160 __flush_work+0x269/0x350 ? __pfx_wq_barrier_func+0x10/0x10 __lru_add_drain_all+0x143/0x1e0 khugepaged+0x65/0x940 ? __pfx_autoremove_wake_function+0x10/0x10 ? __pfx_khugepaged+0x10/0x10 kthread+0xcf/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> I can provide more kernel log if requested. I assume this is an upstream issue, but up until current latest stable Debian kernel as of 2026-05-20 the problem persist. Can't reproduce the issue on 6.12.74+deb13. * What exactly did you do (or not do) that was effective (or ineffective)? Suspend and then resume my laptop. * What was the outcome of this action? When the screen goes black, I can not use my laptop locally as there is no feedback. Closing the laptop lid and opening it again makes the screen go back to normal for a dozen of seconds and it would went black again. * What outcome did you expect instead? Suspend and resuming would work normally. To prevent affecting my daily usage, I have to reboot back into linux-image-6.12.74+deb13+1-amd64 and keep using workarounds of recent LPE CVEs. -- System Information: Debian Release: 13.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.74+deb13+1-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-amd64 depends on: ii linux-image-6.12.88+deb13-amd64 6.12.88-1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information