public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Pavel Ivanov <paivanof@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Full lockup when compiling kernel with "optimal" number of threads
Date: Thu, 06 Oct 2011 12:22:24 +0530	[thread overview]
Message-ID: <4E8D5028.3080406@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAG1a4rvYX9P+vHTLQBV_edViU8QriT=mrut0c5oS5YZ96L3x=A@mail.gmail.com>

On 10/06/2011 03:13 AM, Pavel Ivanov wrote:
> On Mon, Oct 3, 2011 at 5:39 AM, Srivatsa S. Bhat
> <srivatsa.bhat@linux.vnet.ibm.com> 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 <nr_cpus*2> 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.
> 

I was referring to the terms used by kernbench.

-- 
Regards,
Srivatsa S. Bhat  <srivatsa.bhat@linux.vnet.ibm.com>
Linux Technology Center,
IBM India Systems and Technology Lab

      reply	other threads:[~2011-10-06  6:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03  3:34 Full lockup when compiling kernel with "optimal" number of threads Pavel Ivanov
2011-09-30  4:10 ` Pavel Ivanov
2011-10-03  9:38 ` Srivatsa S. Bhat
2011-10-05 21:51   ` Pavel Ivanov
2011-10-03  9:39 ` Srivatsa S. Bhat
2011-10-05 21:43   ` Pavel Ivanov
2011-10-06  6:52     ` Srivatsa S. Bhat [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E8D5028.3080406@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paivanof@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox