Summary: | "emerge" causes OOM-killer even when VM space is available | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Mark <musicman529> |
Component: | Unclassified | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mark
2005-09-12 17:29:06 UTC
This isn't portage's fault, nor problem really. Portage requires a chunk of memory, but nothing that's going to hog a significant portion of mem (compared to firefox fex). OOMK waxes the process hogging the most memory; if you run out of memory, it's going to get killed. plain and simple (this is assuming OOMK is in use). If portage is consuming insane amounts of memory, sure, then there is a problem, but willing to bet it's not. Assuming you're lacking swap also, if oomk is kicking in. Actually, this looks more like your OOMK is being whacky. Bouncing it to kernel crew, either way it's not portage doing it (or you can tar and feather me) :P Can you try to reproduce this with gentoo-sources-2.6.13-r1 and in case this is reproducible in gentoo-sources, try vanilla-sources-2.6.13.1 please? sorry, forgot to mention, vanilla-sources-2.6.14_rc1 will be in portage soon (it's already in CVS) so try with this one too. Do you mean try to get the OOMK while emerging kernel sources, or build the kernel sources and then try to get the OOMK on the new kernel? Build the new kernel, boot it, then reproduce the problem. No worries, Brian. No tar and feathers. Not even tar and bzip2. ;-) I got an OOMK incident today, with having just "too much" open. I don't understand why, as swap was only about 10% used. But running Firefox, Thunderbird, and OpenOffice.org with two documents, then trying to launch Acrobat Reader, ended up zapping acroread. There was no emerge or gcc running on my system. I suppose I need to look into tuning the OOMK. I'll search Google, but if anyone can point me to a document explaining, I would appreciate it greatly. |