On Fri, Mar 19, 2010 at 4:39 AM, Eli Zaretskii <e...@gnu.org> wrote: > > Date: Thu, 18 Mar 2010 16:26:19 -0700 > > From: tom honermann <tom.honerm...@oracle.com> > > Cc: bug-make@gnu.org > > > > > > 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) > > If processes are killed by OOM Killer, there's a prominent message to > that effect in the system logs (/var/log/messages or some such). > Search for "oom" (IIRC) in the log. >
No such thing on any log. Grepped for both "oom" and "IIRC". No new crashes happened after I started using -j 16, and since I don't have time nor experience to debug this I'll leave it alone for a week or two and start getting to know the kernel better and then try debugging it again. Thanks for the help. -- Thiago C. Santini ECP/07
_______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
