On 3/18/2010 2:22 PM, Thiago C. Santini wrote:
Yeah, that was my first thought when using -j, 8 processors each one
with hyper-threading should be optimized with 16 jobs but when testing
it I got better results with 32 jobs and that was working just fine
till last week, so I just sticked to it =p
Is there anyway to find out if it really was a kernel panic? Like a
log or something? Any link to good tutorials about debugging a crash
are welcomed aswell :-) I guessed it was a kernel crash because even
the video signal was killed once(the screen wouldn't show anything at
all).
The real problem is that the machine crashed when there was more than
one person working over ssh and I thought maybe someone was compiling
at the same time as me and that made too many jobs.
You may be falling victim to the kernel OOM killer
(http://linux-mm.org/OOM_Killer)
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
