On Mon 2017-01-16, Florian Siegesmund <sonny@cottman.toppoint.de> wrote: > On Sun 2017-01-15, Florian Siegesmund <sonny@cottman.toppoint.de> wrote: >> On Sun 2017-01-15, Ben Hutchings <ben@decadent.org.uk> wrote: >>> On Sun, 2017-01-15 at 11:05 +0100, Florian Siegesmund wrote: >> >>>> Package: src:linux >>>> Version: 4.8.15-2 >>>> Severity: critical >>>> Tags: upstream >>>> Justification: breaks the whole system > > [...] > >>> Linux 4.9 is said to have better OOM behaviour and is now available in >>> unstable. Can you test whether it works better on this system? >> >> We will see: >> >> HOSTNAME:~# uname -a ; uptime >> Linux kyrrdis 4.9.0-1-686-pae #1 SMP Debian 4.9.2-2 (2017-01-12) i686 GNU/Linux >> 22:35:41 up 10:53, 2 users, load average: 0.28, 0.11, 0.04 >> HOSTNAME:~# > > Looks better on first sight, but not good (still one major kill): Tonight a lot of kills again: LOGHOST:~ # egrep '(HOSTNAME|LXCONTAINER).*kernel' /var/log/syslog > /tmp/syslog-20170117-oom.txt HOSTNAME:~ > uname -a ; uptime; date Linux kyrrdis 4.9.0-1-686-pae #1 SMP Debian 4.9.2-2 (2017-01-12) i686 GNU/Linux 09:35:54 up 1 day, 21:54, 2 users, load average: 0,00, 0,00, 0,00 Tue Jan 17 09:35:54 CET 2017 HOSTNAME:~ > I am switching back to 3.16 for now. Florian -- :wq
Attachment:
syslog-20170117-oom.txt.gz
Description: application/gzip