Bug#1125980:
Known points for bisection:
6.17.13-1 ✅ (true suspend)
6.12.63-1 ❌ (broken suspend)
6.12.57-1 ✅ (non-broken suspend)
It seems there aren't any snapshots between 6.12.57-1 and 6.12.63-1, so I can't find out where this bug started. But I can download the kernel images to find out when the fix came.
Bisection log:
linux-image-6.16.3+deb13-amd64-unsigned 6.16.3-1~bpo13+1 ✅ (true suspend)
linux-image-6.14-amd64-unsigned 6.14.3-1~exp1 ✅ (true suspend)
linux-image-6.13-amd64-unsigned 6.13.7-1~exp1 ✅ (true suspend)
linux-image-6.13-amd64-unsigned 6.13.2-1~exp1 ✅ (true suspend)
linux-image-6.13-rc6-amd64-unsigned 6.13~rc6-1~exp1 ❌❌❌ (fails to boot to GDM, kernel panic'd once)
linux-image-6.13-rc7-amd64-unsigned 6.13~rc7-1~exp1 ❌❌❌ (fails to boot to GDM)
So it looks like 6.13.2 is the earliest snapshot available where suspend is fixed on this laptop. I hope that's helpful.
I guess I can try to do a git bisect next if that's helpful?
Reply to: