Your message dated Thu, 01 May 2025 14:33:54 +0200 (CEST) with message-id <20250501123354.a71b6be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #939170, regarding linux: does not suspend completely, locks up 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 ow...@bugs.debian.org immediately.) -- 939170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: linux Version: 5.2.9-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Since the update from 4.19 to 5.2.9 my Lenovo Thinkpad E460 no longer suspends properly. If I close the lid or chose Suspend from the KDE launcher, the system will start to suspend but never reaches standby. Power light will blink as usual, display backlight turns off but keyboard LEDs don't turn off, fan is still active. The system doesn't respond to Ctrl-Alt-Del or change to a Terminal. No input changes anything. Waiting (30min) doesn't help either. Rebooting to Kernel 4.19 fixes the problem immediatly. Expected outcome would be a complete suspend/standby state and a complete recovery/powerup on lid open or press of any key. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (20, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Hi This bug was filed for a (very) old kernel or the bug is old itself without resolution. Maybe it was for a feature enablement which nobody acted on. We are sorry we were not able to timely deal with this issue. There are many open bugs for the src:linux package and thus we are closing older bugs where it's unclear if they still occur in newer versions and are still relevant to the reporter. For an overview see: https://bugs.debian.org/src:linux . If you can reproduce your issue with - the current version in unstable/testing - the latest kernel from backports or, if it was a feature addition/wishlist and still consider it relevant, then: Please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Please try to provide as much fresh details including kernel logs where relevant. In particular were an issue is coupled with specific hardware we might ask you to do additional debugging on your side as the owner of the hardware. Regards, Salvatore
--- End Message ---
