On 2025-03-12 at 06:34:43, Salvatore Bonaccorso wrote: > What is that range? Could you next bisect. Assuming we get even a > result within one stable series, this would be great, because then > next I would like to ask if you can bisect the respective upstream > changes to the breaking commits (still works if the issue is > introduced on major version change, then bisect might take longer). I've done some testing and I've found that 6.10.12 is the last good version and 6.11-rc4 is the first bad version. The former resumes correctly from suspend and hibernate and the latter fails in both cases. I also tested suspend on 6.11.2 and 6.11.10 and they also failed. In all cases, to test suspend, I booted the machine on the kernel in question, logged in, waited for Firefox (which is loaded as part of my session) to finish loading the snapshot.debian.org page, then suspended by closing the lid. To test hibernate, I went to the MATE shutdown menu and chose "Hibernate" instead of closing the lid. Resuming from hibernation was done by booting the default kernel (which is presently 6.13.6 from experimental), although of course that kernel is overwritten by the one from the hibernation. One interesting detail which may or may not be relevant is that suspend on 6.11 takes much longer, around 5 to 10 seconds before the light on the lid begins to pulse. It is much faster on 6.10.12. I'm including all of the kernel logs from my tests today (and from intermediate boots to install new kernels) as a gzipped attachment (firewall logs excluded for privacy and because they aren't relevant to this matter). -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
kern.log.gz
Description: application/gzip
Attachment:
signature.asc
Description: PGP signature