Fixed upstream and in Debian linux-image-6.1.0-20-amd64
I bisect the upstream kernel to find the bad commit:
git bisect start
# status: waiting for both good and bad commits
# good: [2dde18cd1d8fac735875f2e4987f11817cc0bc2c] Linux 6.5
git bisect good 2dde18cd1d8fac735875f2e4987f11817cc0bc2c
# status: waiting for bad commit, 1 good commit known
# bad:
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=218538
I compiled the kernel 6.1.76 from Debian sources without applying any patch and
it can't wake up from suspend :-( May be there is an specific driver or module
that needs to be compiled for sedutil to work properly on waking up from S3.
I changed just the disk of the notebook and installed Debian 12 on it, without
any encryption and suspend works fine on kernel 6.1.0-18.
Which makes me conclude that something is wrong with some patch of that Debian
kernel, not allowing the disk to be decrypted with sedutil after waking up. I
New try: I recompiled sedutil after booting linux-image-6.1.0-18-amd64 (git
clone --branch s3-sleep-support https://github.com/badicsalex/sedutil.git). It
made no difference, i.e., I still can't get the machine to fully wake up.
(sedutil compiled at linux-image-6.1.0-18-amd64 still works fine
Adding "intel_iommu=off" to kernel boot does NOT change anything.
Adding "init_on_alloc=0" to kernel boot does NOT change anything.
The bug still persists with the linux-image-6.1.0-18-amd64.
Changing /etc/systemd/sleep.conf to have "SuspendState=standby" or
"SuspendState=freeze" seems to make things worse because the notebook seems
unable to enter sleep mode, while "SuspendState=mem" causes the same behavior
as reported here, i. e., the notebook seems unable to wake up from
The bug first appeared in linux-image-6.1.0-14-amd64 and persists through
linux-image-6.1.0-15-amd64, linux-image-6.1.0-16-amd64 and
linux-image-6.1.0-17-amd64.
--
André Desgualdo Pereira
If I use "echo mem > /sys/power/state" instead of systemctl to suspend, the
result is the same, ie, the notebook doesn't seem to fully wake up, when trying
to wake up from suspend, the screen stays black.
The CAPS LOCK led doesn't change when pressing the CAPS LOCK button, but the
computer can
sedutil seems to be working
`$ cat /sys/module/libata/parameters/allow_tpm` result "1"
and
`sedutil-cli --scan` shows the disk correctly ("/dev/sda2 KINGSTON
SKC600256G S4800105")
If there are any further tests that can help elucidate the problem, please let
me
1. I tested booting with the kernel option "nomodeset", it made no difference.
2. I tested suspend by writing to /sys/power/pm_test the following successively
"freezer", "devices", "platform", "processors", "core". Every single test was
successful, ie, the system wake up on its own after 5
Package: src:linux
Version: 6.1.67-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Updating the kernel
* What exactly did you do (or not do) that
15 matches
Mail list logo
