El 17/1/20 a les 19:31, Rogério Brito ha escrit:
Source: linux
Version: 4.19.67-2+deb10u2
Severity: important
X-Debbugs-CC: debian-...@lists.debian.org
Hi, Ben and others.
I've been getting some OOM errors on my armel/kirkwood device running Debian
stable. One of the reasons for this is, according to the dmesg logs, that
COMPACT (memory compaction) is tried, but not available:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
$ grep -i compact /boot/config-4.19.0-6-marvell
# CONFIG_COMPACTION is not set
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I'm running debian stretch on a lacie network space 2 (armel/kirkwood)
and lately I'm seeing a lot of OOM errors, however I'm not sure it's
just a problem of CONFIG_COMPACTION: the previous kernel had it not set
either and I don't remember experiencing that many OOM.
I'm seeing them just after the latest kernel update I made on February 9
2020. It's possible that I just missed them previously, though I doubt
it since this machine is doing too many things and I would have noticed
if some vital process stopped.
The remnant of the kernel (3.16.0) in jessie that I still have on this
machine had CONFIG_COMPACTION enabled.
$ grep -i compact /boot/config*
/boot/config-3.16.0-8-kirkwood:CONFIG_COMPACTION=y
/boot/config-4.9.0-11-marvell:# CONFIG_COMPACTION is not set
/boot/config-4.9.0-12-marvell:# CONFIG_COMPACTION is not set
Bye
--
Luca
