All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Pavel Ivanov <paivanof@gmail.com>
Cc: ecryptfs@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Full lockup when compiling kernel with "optimal" number of threads
Date: Mon, 03 Oct 2011 15:08:12 +0530	[thread overview]
Message-ID: <4E898284.7060906@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAG1a4rvdYnOSWu3DJ+DL+Q_bfsfTv_px20vP06fBKRm6B8cwMw@mail.gmail.com>

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@linux.vnet.ibm.com>
Linux Technology Center,
IBM India Systems and Technology Lab

  parent reply	other threads:[~2011-10-03  9:38 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 [this message]
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

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=4E898284.7060906@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=ecryptfs@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.