Re: oomkillers gone wild.

[David Rientjes]

On Tue, 5 Jun 2012, Dave Jones wrote:

> Still doesn't seem right..
> 
> eg..
> 
> [42309.542776] [ pid ]   uid  tgid total_vm      rss cpu oom_adj oom_score_adj name
> ..
> [42309.553933] [  500]    81   500     5435        1   4     -13          -900 dbus-daemon
> ..
> [42309.597531] [ 9054]  1000  9054   528677    14540   3       0             0 trinity-child3
> ..
> 
> [42309.643057] Out of memory: Kill process 500 (dbus-daemon) score 511952 or sacrifice child
> [42309.643620] Killed process 500 (dbus-daemon) total-vm:21740kB, anon-rss:0kB, file-rss:4kB
> 
> and a slew of similar 'wrong process' death spiral kills follows..
> 

On a system not under oom conditions, i.e. before you start trinity, can 
you send the output of

	cat /proc/$(pidof dbus-daemon)/oom_score{_adj,}
	grep RSS /proc/$(pidof dbus-daemon)/status
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/