[Bugme-new] [Bug 42102] New: OOM killer kills incorrect and too many processes
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Aug 30 11:03:12 PDT 2011
https://bugzilla.kernel.org/show_bug.cgi?id=42102
Summary: OOM killer kills incorrect and too many processes
Product: Memory Management
Version: 2.5
Kernel Version: 3.0.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Other
AssignedTo: akpm at linux-foundation.org
ReportedBy: dreisner at archlinux.org
Regression: No
Created an attachment (id=70912)
--> (https://bugzilla.kernel.org/attachment.cgi?id=70912)
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.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Bugme-new
mailing list