From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Srivatsa S. Bhat" Subject: Re: Full lockup when compiling kernel with "optimal" number of threads Date: Mon, 03 Oct 2011 15:09:47 +0530 Message-ID: <4E8982E3.9080809@linux.vnet.ibm.com> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Received: from e28smtp01.in.ibm.com ([122.248.162.1]:55597 "EHLO e28smtp01.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754004Ab1JCJju (ORCPT ); Mon, 3 Oct 2011 05:39:50 -0400 In-Reply-To: Sender: ecryptfs-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Pavel Ivanov Cc: ecryptfs@vger.kernel.org, linux-kernel 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: > By the way "optimal" is supposed to be make -j isn't it? IIRC, "maximal" refers to make -j -- Regards, Srivatsa S. Bhat Linux Technology Center, IBM India Systems and Technology Lab