Bug 42102 - OOM killer kills incorrect and too many processes
Summary: OOM killer kills incorrect and too many processes
Status: RESOLVED OBSOLETE
Alias: None
Product: Memory Management
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 high
Assignee: David Rientjes
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-30 18:03 UTC by Dave Reisner
Modified: 2012-08-30 13:30 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.0.1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
full log of oom-killer activity (40 bytes, text/plain)
2011-08-30 18:03 UTC, Dave Reisner
Details

Description Dave Reisner 2011-08-30 18:03:09 UTC
Created attachment 70912 [details]
full log of oom-killer activity

I woke up this morning to discover that the OOM killer was invoked 23 times, taking down a large number of processes. This is a self-configured x86_64 kernel running on 12GB of RAM. Particularly concerning in the attached log is:

- It doesn't seem obvious to me where I was out of memory. git (gc cron job) is the only suspicious process, but the RSS at the time doesn't look at all dangerous.
- Processes with an extremely low oom_score_adj were nuked. In particular, polkit and dbus-daemon, with a score of -900, were taken down. Much to my dismay, tmux, mutt, mpd and a tail of my syslog were all survivors of this.

Other possibly related:

- I'm using systemd, so cgroups are involved.
- I do enable KSM, but at the time I had no VMs running and no shared pages merged.
- BZ#39452 seems related, but the OP says the behavior is fixed in 3.0.1.
- .config: http://pkgbuild.com/~dreisner/config
- commit 3a5dda7a17cf3706f79b86293f29db02d61e0d48 -- just pointing out a recent behavioral change. not sure if this is relevant.
- dmesg: http://pkgbuild.com/~dreisner/dmesg.log -- this has some of the oom-killer activity picked up after syslog-ng died.

Note You need to log in before you can comment on or make changes to this bug.