Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #92700

Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume

Cross-posted to 2 groups.

Show all headers | View raw

Hi Bill,

On 5/22/26 20:50, Bill Allombert wrote:
> On Tue, May 05, 2026 at 07:51:45PM +0200, Bill Allombert wrote:
>> On Tue, May 05, 2026 at 06:43:30PM +0200, Bill Allombert wrote:
>>> On Tue, May 05, 2026 at 05:33:40PM +0200, Salvatore Bonaccorso wrote:
>>>> Hi Bill,
>>>> Maybe already ahead: Can you provide the crash log?
>>>
>>> How do I do that reliably ?
>>>
>>> For what I see, it crashes just after 
>>> kernel: PM: hibernation: hibernation exit
>>
>> In fact it is even weirder:
>> 'echo disk > /sys/power/state' -> it hibernates
>> First restart -> it resumes (displays the correct screen) and then halts
>> Second restart -> it resumes again and then FAIL.
>>
>> I tried some other kernels from snapshot.debian.org
>>
>> 6.1.0-44        -> very good
>> 6.5.0-0.deb12.4 -> good 
> 
> 6.7.12-1~bpo12+1 -> OK
> 
> 6.8.9 -> exit hibernation immediatly, does not halt (bad)
> 6.8.12-1 -> idem (bad)
> 
> I note that if we do 'echo disk > /sys/power/state' repeatedly, then it
> crashes but after a hard reboot it recovers the state correctly!
> 
>> 6.10.11+bpo     -> exit hibernation immediatly, does not halt (bad)
>> 6.12.9+bpo      -> idem (bad)
>> 6.12.43+deb12   -> idem (bad)
>> 6.12.69+deb12   -> idem (bad)
>> 6.12.74+deb12   -> idem (bad)
> 
> 7.0.7+deb13 -> suspend but does not recover.
> 
> Cheers,


Thanks for the bisection effort -- narrowing it to 6.7 OK -> 6.8 bad is
useful.

However, We still need more information to move forward. I understand
collecting logs is difficult when the machine appears dead after resume,
so here is a guide broken into steps.

(1) Provide fresh system information

We do not have your exact machine. We need hardware, driver, and
firmware details to cross-reference changes between 6.7 and 6.8.

Please attach the output of the following (from a fresh boot with a
failing kernel):

  uname -a
  cat /proc/cpuinfo | head -20
  lspci -nnk
  lsmod
  dmesg > dmesg-fresh-boot.log
  journalctl -b 0 > journal-fresh-boot.log
  fwupdmgr get-devices

You can check it from previous mailing thread from
Salvatore and TJ (Thanks!):

---

On 5/5/26 17:33, Salvatore Bonaccorso wrote:
>>>[snip]
>>>
>>> I upgraded from bookworm to trixie and now suspend-to-disk does not work correctly anymore.
>>>
>>> echo disk > /sys/power/state
>>> suspend the computer,
>>> it seems to resume correclty but then immediatly crashes.
>>>
>>> My laptop is a Dell latitude 5410.
>>
>> Before we start into deeper debugging, can you check if like for
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135599#51 reverting
>> the offending commit fixes your issue?
>>
>> The offending commit went in almost all stable series, 6.12.75 has it
>> as well, so the current trixie kernel.
> 
> Maybe already ahead: Can you provide the crash log?
> 
> Regards,
> Salvatore


On 5/21/26 09:42, Tj wrote:
> Package: linux-image-7.0.9+debian+tj
> Followup-For: Bug #1135748
> X-Debbugs-Cc: tj.iam.tj@proton.me
> 
> Bill, can you provide a fresh boot kernel log and output of `lspci -nnk`
> (for any kernel version that fails a hibernation resume).
> 
> You can get a list of boot session UUIDs and the kernel used with
> `journalctl --grep 'Linux version' `
> 
> Then use `journalctl --boot ${UUID} > dmesg.log `


---


(2) Determine if the kernel panics or only the display freezes


Before setting up crash dumps, check whether the kernel is actually dead
or just the display stopped updating.

Before triggering hibernate, start a persistent log watcher:

  journalctl -kf > /tmp/hibernate-watch.log 2>&1 &

Then trigger your scenario. After the machine appears stuck, from
another machine on the same network:

  ping <your-laptop-ip>

If it responds: the kernel is alive, only the display is frozen. You can
SSH in and collect logs (journalctl, dmesg).

If it does not respond: the kernel has likely panicked. Proceed to
step 3.


(3) Capture crash dump with kdump

If the machine is completely unresponsive (no ping), install kdump to
capture the panic log:

  sudo apt install kdump-tools

Reboot once after installation (kdump reserves memory at boot). Then
reproduce your hibernate scenario. If the kernel panics, kdump will
write a dump to /var/crash/. After the machine reboots:

  ls /var/crash/

Attach the dmesg file from that crash directory. If you can also attach
the full vmcore dump, even better, but the dmesg alone is sufficient to
start.


With the hardware info from step 1 and the bisection range (6.7 -> 6.8),
we can look at the specific commits affecting your hardware. The logs or
crash dump will tell us exactly what is failing on resume.


Sorry for the late reply! :)

Best Regards,
Yunseong

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <ballombe@debian.org> - 2026-05-05 15:50 +0200
  Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Salvatore Bonaccorso <carnil@debian.org> - 2026-05-05 17:30 +0200
    Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Salvatore Bonaccorso <carnil@debian.org> - 2026-05-05 17:40 +0200
      Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Salvatore Bonaccorso <carnil@debian.org> - 2026-05-05 17:50 +0200
      Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <ballombe@debian.org> - 2026-05-05 18:50 +0200
        Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <ballombe@debian.org> - 2026-05-05 20:00 +0200
          Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <ballombe@debian.org> - 2026-05-12 22:00 +0200
          Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <ballombe@debian.org> - 2026-05-22 21:00 +0200
            Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Yunseong Kim <ysk@kzalloc.com> - 2026-05-23 11:20 +0200
            Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Yunseong Kim <ysk@kzalloc.com> - 2026-05-23 11:20 +0200
              Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <Bill.Allombert@math.u-bordeaux.fr> - 2026-05-23 11:40 +0200
                Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Yunseong Kim <ysk@kzalloc.com> - 2026-05-23 12:00 +0200
                Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <Bill.Allombert@math.u-bordeaux.fr> - 2026-05-23 13:30 +0200
                Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Yunseong Kim <ysk@kzalloc.com> - 2026-05-23 13:40 +0200
  Processed: Re: Bug#1135748: linux-image-6.12.85+deb13-amd64:  suspend to disk crashes after resume "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-05-05 17:30 +0200
  Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Tj <tj.iam.tj@proton.me> - 2026-05-21 09:50 +0200
  Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Yunseong Kim <ysk@kzalloc.com> - 2026-05-23 14:10 +0200
    Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <ballombe@debian.org> - 2026-05-23 14:20 +0200
      Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Yunseong Kim <ysk@kzalloc.com> - 2026-05-23 18:20 +0200
        Bug#1135748: linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume Bill Allombert <ballombe@debian.org> - 2026-05-23 20:30 +0200

csiph-web