Comment # 47 on bug 1165351 from Luis Chamberlain

(In reply to Thomas Blume from comment #46)
> You can see ps 4610 is consuming about 16MB, which is just fine for 2G of
> RAM.
> 
> Maybe it is bound to big memory machines?
> Could you give it a try rebooting one of your machines with reducing the
> physical memory size using the mem kernel parameter?


I enforced mem=2G and the oom still triggers. I left the system booted with 2G
, you can feel free to edit as you see fit. You do this by editing
/etc/default/grub and then modifying the line that has the existing mem=2G
line, which is GRUB_CMDLINE_LINUX_DEFAULT. To make it take effect on next boot,
run:

sudo update-bootloader


mcgrof@chivo ~ $ free -h
              total        used        free      shared  buff/cache   available
Mem:          1.6Gi       638Mi       915Mi       0.0Ki        89Mi       885Mi
Swap:         1.0Gi        35Mi       988Mi
mcgrof@chivo ~ $ sudo dmesg| grep oom
[ 2465.363645] (systemd) invoked oom-killer:
gfp_mask=0x100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), order=0, oom_score_adj=0
[ 2465.705200]  oom_kill_process.cold+0xb/0x10
[ 2468.573932] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents
oom_score_adj name
[ 2471.181285]
oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/init.scope,task=(systemd),pid=2376,uid=0
[ 2471.299473] Out of memory: Killed process 2376 ((systemd))
total-vm:54694760kB, anon-rss:952556kB, file-rss:2200kB, shmem-rss:0kB, UID:0
pgtables:3904kB oom_score_adj:0
[ 2471.483078] oom_reaper: reaped process 2376 ((systemd)), now anon-rss:0kB,
file-rss:0kB, shmem-rss:0kB
mcgrof@chivo ~ $ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-5.5.4-1-default
root=UUID=22cf9d5d-e128-41a2-8311-4f735a1d1352 console=tty0 console=ttyS0,57600
sysrq_always_enabled panic=100 ignore_loglevel unknown_nmi_panic
resume=/dev/disk/by-id/scsi-3300143804052b801-part2 mem=2G mitigations=auto
crashkernel=512M-2G:128M,2G-64G:256M,64G-:512M