From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935364Ab1JEVny (ORCPT ); Wed, 5 Oct 2011 17:43:54 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:65412 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756259Ab1JEVnx (ORCPT ); Wed, 5 Oct 2011 17:43:53 -0400 MIME-Version: 1.0 In-Reply-To: <4E8982E3.9080809@linux.vnet.ibm.com> References: <4E8982E3.9080809@linux.vnet.ibm.com> From: Pavel Ivanov Date: Wed, 5 Oct 2011 17:43:22 -0400 Message-ID: Subject: Re: Full lockup when compiling kernel with "optimal" number of threads To: "Srivatsa S. Bhat" Cc: linux-kernel Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 3, 2011 at 5:39 AM, Srivatsa S. Bhat wrote: > 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 I'm sure I didn't make up that word "optimal" by myself. I took it from some documentation or internet, although now I can't find where I took it from. Wherever I look it says that -j is "unbounded" number of threads. Pavel