Hello Ben, On Tue 2017-01-17, Florian Siegesmund <so...@cottman.toppoint.de> wrote: > On Mon 2017-01-16, Florian Siegesmund <so...@cottman.toppoint.de> wrote: >> On Sun 2017-01-15, Florian Siegesmund <so...@cottman.toppoint.de> wrote: >>> On Sun 2017-01-15, Ben Hutchings <b...@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: > > [...] > > I am switching back to 3.16 for now.
I gained NFS locking issues running 3.16 kernel from stable on an otherwise up to date testing system, so I tried 4.9 kernel from unstable and drop_caches cronjob workaround. Worked for 6 days before failing: LOGHOST:~ # egrep '(HOSTNAME|LXCONTAINER).*kernel' /var/log/syslog* | sed -e 's/^[^:]*://' | sort > /tmp/syslog-20170128-oom.txt HOSTNAME:~ > uname -a ; uptime; date Linux HOSTNAME 4.9.0-1-686-pae #1 SMP Debian 4.9.2-2 (2017-01-12) i686 GNU/Linux 13:00:02 up 6 days, 22:22, 1 user, load average: 0,08, 0,08, 0,02 Sat Jan 28 13:00:02 CET 2017 HOSTNAME:~ > Best Regards Florian -- :wq
syslog-20170128-oom.txt.gz
Description: application/gzip
