Re: Full lockup when compiling kernel with "optimal" number of threads

From: Srivatsa S. Bhat
Date: Thu Oct 06 2011 - 02:52:32 EST


On 10/06/2011 03:13 AM, Pavel Ivanov wrote:
> On Mon, Oct 3, 2011 at 5:39 AM, Srivatsa S. Bhat
> <srivatsa.bhat@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxx>
Linux Technology Center,
IBM India Systems and Technology Lab
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/