Re: oomkillers gone wild.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]