Re: Full lockup when compiling kernel with "optimal" number of threads

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



On 09/03/2011 09:04 AM, Pavel Ivanov wrote:
> Hi,
> 
> I can reliably reproduce a complete machine lockup when compiling
> kernel sources with "make -j". After making some progress machine
> stops responding to anything (including CapsLock/NumLock switching or
> mouse moving) and after hard reboot nothing is left in kern.log or
> syslog. Only attaching a serial console gives me the following clues
> to what happens:
> 

[...]

> After that only doing "make distclean" allows me to compile kernel
> again. And note that when I build with "make -j 10" everything works
> fine (I have 2 CPUs with 4 cores each without hyper-threading).

How much memory does your system have? Doing so many fork()s could cause
a lot of resource conflict and memory pressure leading to heavy swapping
etc., which can ultimately hang your system, especially when your RAM
size is small. It is advisable to use make -j only on systems with lot
of RAM (> 3 or 4GB).

-- 
Regards,
Srivatsa S. Bhat  <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
Linux Technology Center,
IBM India Systems and Technology Lab
--
To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]

Powered by Linux