From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754173Ab1JCJiU (ORCPT ); Mon, 3 Oct 2011 05:38:20 -0400 Received: from e28smtp07.in.ibm.com ([122.248.162.7]:54770 "EHLO e28smtp07.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753891Ab1JCJiO (ORCPT ); Mon, 3 Oct 2011 05:38:14 -0400 Message-ID: <4E898284.7060906@linux.vnet.ibm.com> Date: Mon, 03 Oct 2011 15:08:12 +0530 From: "Srivatsa S. Bhat" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:6.0.2) Gecko/20110906 Thunderbird/6.0.2 MIME-Version: 1.0 To: Pavel Ivanov CC: ecryptfs@vger.kernel.org, linux-kernel Subject: Re: Full lockup when compiling kernel with "optimal" number of threads References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 Linux Technology Center, IBM India Systems and Technology Lab