[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1021581: marked as done (linux-image-amd64: 5.18 regression: hibernate works but does not power off computer)



Your message dated Wed, 26 Nov 2025 00:47:06 +0100 (CET)
with message-id <[🔎] 20251125234706.A4A71BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1021581,
regarding linux-image-amd64: 5.18 regression: hibernate works but does not power off computer
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.)


-- 
1021581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021581
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 6.0~rc7-1~exp1
Severity: important
Tags: upstream
X-Debbugs-Cc: patj@posteo.de

Dear Maintainer,

Upgrading the kernel from 5.17 to 5.18 (and also tested with 5.19.11-1, 6.0~rc7) introduced the following hibernation bug:

If I enter hibernation via "systemctl hibernate" or any other method mentioned at the kernel doc Documentation/power/basic-pm-debugging.rst the hibernation state of the system is completed but the computer itself stays powered on.
The computer is unusable in this state. I have a frozed cursor with the last screen visible before the hibernation.
After force killing the computer and powering back on the system state is completely recovered, hence the hibernation worked basically.

Using kernel 5.17.3-1 everything is fine: hibernate works and the computer powers off as it should be.

An internet research found this similar regression https://lore.kernel.org/lkml/YqE22nS9k2+AldI6@llamedos.localdomain/ but the fix does not apply to my machine.

My machine:
Dell Inspiron 7590
Intel i7-9750H
Nvidia GTX 1050

What can I provide to debug this problem?

Best,
Patrick


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-rc7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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.0.0-rc7-amd64  6.0~rc7-1~exp1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

--- 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 ---

Reply to: