Re: Why oom killer?

[Kamil Jońca <kjonca@o2.pl>]

Michael Stone <mstone@debian.org> writes:

> On Tue, Sep 30, 2025 at 04:29:44PM +0200, Kamil Jońca wrote:
>>Debian sid laptop: Recently during backup (==zstd process compressing
>>content, but I am not sure I started to get processes be killed by oom
>>killer)
>>Laptop has 20GM RAM + 32G swap, no one is working on it, only xdm is
>>launched.
>
> What does "free" report, and what is the output of "dmesg | grep Memory:"?
> I don't see anywhere near 20GB of memory accounted for in your log.
>

In dmesg this info is already gone, so:

%sudo grep Memory /var/log/syslog
[...]
2025-09-30T18:30:10.439375+02:00 mysz kernel: DMI: Memory slots populated: 2/8
2025-09-30T18:30:10.439966+02:00 mysz kernel: Memory: 20048344K/20766008K available (16707K kernel code, 3261K rwdata, 12300K rodata, 4364K init, 5652K bss, 701516K reserved, 0K cma-reserved)
2025-09-30T18:30:10.439970+02:00 mysz kernel: x86/mm: Memory block size: 128MB

%free
               total        used        free      shared  buff/cache   available
Mem:        20277892    20101304      176588         164       30304      176588
Swap:       33554428     1993880    31560548


KJ
-- 
http://wolnelektury.pl/wesprzyj/teraz/
You will be awarded a medal for disregarding safety in saving someone.