On 2025-03-15 at 15:11:07, Salvatore Bonaccorso wrote:
> Okay that is already great, thank you for the time.
> 
> Now the next would in this case be ideally to bisect mainline between
> v6.10 and v6.11-rc4 to identify the commit. On each step to build a
> deb package for the kernel are hilighted at:
> https://wiki.debian.org/DebianKernel/GitBisect

These directions were very helpful in compiling a kernel.
Unfortunately, it led to some unusual results.

The first step in the bisect was to try the merge base, which was 6.10,
which was bad, at which point Git refused to continue because the
problem had been fixed on the v6.10 branch.  So I thought I'd try
Debian's 6.9.2, which worked.  Then I tried upstream 6.9, which also
failed.  To verify, I tried upstream 6.9.2, which failed as well.

Note that I used `make oldddefconfig` with Debian's config to configure
the kernel, stepping back from v6.11-rc4, so it's nearly identical to
the Debian kernel (it's not signed and it doesn't have debug info, but
otherwise it should be pretty much the same.  In all cases, the tooling
is whatever's in Debian unstable at the moment.

My conclusion is thus that Debian includes some patch in the 6.9 and
6.10 series that fixes suspend and hibernate, but that patch is not
included in 6.11 and newer.

I will point out that I have a very similar ThinkPad X1 Carbon Gen 10
for work running Ubuntu 24.04 and their 6.8 kernel, and suspend and
resume do work there (the machine is using Secure Boot, so I cannot
speak to hibernation).  I can try booting off a live Ubuntu 24.10 image
(which contains a 6.11 kernel) or a daily build of Ubuntu 25.04 (which
contains a 6.14 kernel) and report back if you think that would be
helpful, say, in isolating an appropriate patch to apply.  I mention
this mostly because I know they do routine testing for things like
suspend and resume on some ThinkPads, so presumably things do work
there.

Of course, if you've come to a different conclusion or have other
suggestions about how to identify a cause, I'm all ears.
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA

Attachment: signature.asc
Description: PGP signature

Reply via email to