#1127588 linux-image-6.18.9+deb14-amd64: Cannot hibernate after some time of work

Package:
src:linux
Source:
src:linux
Submitter:
Kamil Jońca
Date:
2026-06-08 04:45:02 UTC
Severity:
normal
Tags:
#1127588#5
Date:
2026-02-10 05:15:00 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
After some time of work I tried to hibernate my computer. From my
observation this problem appears after some memeory consyuming tasks
(like using xz or zstd on big data with aggressive compression options)


   * What was the outcome of this action?
  Computer cannot hibernate. In logs I have:

[...]
2026-02-10T05:58:34.319759+01:00 dorsz kernel: PM: hibernation: Basic memory bitmaps created
2026-02-10T05:58:34.319760+01:00 dorsz kernel: PM: hibernation: Preallocating image memory
2026-02-10T05:58:34.319760+01:00 dorsz kernel: PM: hibernation: Image allocation is 2704661 pages short
[...]
Apart from that:

%free
               total        used        free      shared  buff/cache   available
Mem:        32312684    30358816      284812      329212      686804     1953868
Swap:       46874620    20103436    26771184

   * What outcome did you expect instead?
under kernel 6.12.x in the same situation swap is almost entirely free,
and hibernation works.

*** End of the template - remove these template lines ***

#1127588#12
Date:
2026-03-13 09:10:18 UTC
From:
To:
I also get this problem with 6.19.6+deb14-amd64 on different machine.
#1127588#19
Date:
2026-05-14 04:12:56 UTC
From:
To:
With kernel:
Linux dorsz 7.0.4+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 7.0.4-1 (2026-05-07) x86_64 GNU/Linux
problem still persists:

2026-05-14T06:05:16.432907+02:00 dorsz kernel: PM: hibernation: Image allocation is 2015391 pages short

#1127588#24
Date:
2026-05-24 07:36:07 UTC
From:
To:
mostly used.  So hibernate fails are expected.

The question we need to solve now is: what is using up all this memory.
Not much is used up for file cache and so.  There could be a memory leak
somewhere.  But to determine that we need more information.

Please provide the contents of:
- /proc/meminfo
- /proc/slabinfo

Bastian

#1127588#29
Date:
2026-05-24 18:45:28 UTC
From:
To:
Bastian Blank <waldi@debian.org> writes:

In attchaments results for
%uname -r
6.12.85+deb13-amd64

#1127588#36
Date:
2026-05-28 15:16:32 UTC
From:
To:
Today I could not hibernbate.
slabinfno and meminfo for 7.0.9+deb14-amd64  in attachments

#1127588#41
Date:
2026-06-01 14:07:24 UTC
From:
To:
In attachment info for 7.0.10+deb14-amd64
#1127588#48
Date:
2026-06-08 04:43:48 UTC
From:
To:
I am not sure if this is related, but on other machine running 7.0.10
kernel I got:
--8<---------------cut here---------------start------------->8---
2026-06-07T19:05:58.084795+02:00 alfa kernel: filter-msgid-sq invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
2026-06-07T19:06:00.343571+02:00 alfa kernel: CPU: 4 UID: 9 PID: 4035101 Comm: filter-msgid-sq Not tainted 7.0.10+deb14-amd64 #1 PREEMPT(lazy)  Debian 7.0.10-1
2026-06-07T19:06:07.567116+02:00 alfa kernel: Hardware name: Gigabyte Technology Co., Ltd. B450 AORUS PRO/B450 AORUS PRO-CF, BIOS F66 10/28/2025
2026-06-07T19:06:09.233440+02:00 alfa kernel: Call Trace:
2026-06-07T19:06:10.394172+02:00 alfa kernel:  <TASK>
2026-06-07T19:06:11.292049+02:00 alfa kernel:  dump_stack_lvl+0x5d/0x80
2026-06-07T19:06:12.149128+02:00 alfa kernel:  dump_header+0x43/0x1b3
2026-06-07T19:06:12.733632+02:00 alfa kernel:  oom_kill_process.cold+0xa/0xb7
2026-06-07T19:06:13.269507+02:00 alfa kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
2026-06-07T19:06:14.347009+02:00 alfa kernel:  out_of_memory+0x210/0x510
2026-06-07T19:06:14.722764+02:00 alfa kernel:  __alloc_pages_slowpath.constprop.0+0xfc9/0x1250
2026-06-07T19:06:15.054413+02:00 alfa kernel:  ? psi_task_switch+0x131/0x390
2026-06-07T19:06:15.303993+02:00 alfa kernel:  __alloc_frozen_pages_noprof+0x32d/0x340
2026-06-07T19:06:15.768227+02:00 alfa kernel:  alloc_pages_mpol+0x86/0x190
2026-06-07T19:06:15.990728+02:00 alfa kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
2026-06-07T19:06:16.676622+02:00 alfa kernel:  folio_alloc_mpol_noprof+0x14/0x40
2026-06-07T19:06:17.416621+02:00 alfa kernel:  swap_cache_alloc_folio+0x8b/0xe0
2026-06-07T19:06:17.869796+02:00 alfa kernel:  swapin_readahead+0x1c6/0x5e0
2026-06-07T19:06:18.197846+02:00 alfa kernel:  do_swap_page+0x91d/0x1850
2026-06-07T19:06:18.574688+02:00 alfa kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
2026-06-07T19:06:18.842775+02:00 alfa kernel:  ? do_fault+0x353/0x5c0
2026-06-07T19:06:19.195947+02:00 alfa kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
2026-06-07T19:06:19.513064+02:00 alfa kernel:  __handle_mm_fault+0x9fa/0xf50
2026-06-07T19:06:20.046454+02:00 alfa kernel:  handle_mm_fault+0xe7/0x2d0
2026-06-07T19:06:20.595357+02:00 alfa kernel:  do_user_addr_fault+0x2b4/0x7b0
2026-06-07T19:06:21.031715+02:00 alfa kernel:  exc_page_fault+0x82/0x1d0
--8<---------------cut here---------------end--------------->8---

After that I was not able to connect to machine (and this was last log
entry before hard reset :(

Machine in question has 30Gi memory + 100Gi swap and has no memory
consuming processes.


KJ