Hi Bill, On 5/23/26 11:29, Bill Allombert wrote: > On Sat, May 23, 2026 at 11:16:45AM +0200, Yunseong Kim wrote: >> Hi Bill, >> >> Thanks for the bisection effort -- narrowing it to 6.7 OK -> 6.8 bad is >> useful.
I remember you mentioned: --- 6.1.0-44 -> very good 6.5.0-0.deb12.4 -> good 6.10.11+bpo -> exit hibernation immediatly, does not halt (bad) 6.12.9+bpo -> idem (bad) --- 6.7.12-1~bpo12+1 -> OK 6.8.9 -> exit hibernation immediatly, does not halt (bad) 6.8.12-1 -> idem (bad) --- I think you can share either 6.10.11+bpo or 6.8.9. I suspect those versions also have the similar issue. > The problem with the bisection is that the behaviour changed between 6.12.74 > and 6.12.86, > 6.12.74 does not suspend but recover (after a hard shutdown) while > 6.12.86 suspends recover but then stop. > > So which kernel should I use for reporting the log ? It seems that both versions have issues. Could you please share each 2 items information? I those kernel maybe hung not panicked. > On 5/21/26 09:42, Tj wrote: >> Package: linux-image-7.0.9+debian+tj >> Followup-For: Bug #1135748 > > Thanks, I did not receive this mail, I was not CCed. > > Cheers, > Bill. I want to check whether the kernel is still alive or has panicked and crashed. * Don't forget to sharing fresh information: hardware, driver, firmware mentioned at the previous thread. * Don't forget to set it up before triggering hibernation, start a persistent log watcher: journalctl -kf > /<e.g., your $HOME>/hibernate-watch.log 2>&1 & I've updated the command because it was confusing in the /tmp directory. Regards, Yunseong
