public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Linux 2.6.22-rc2: make -j makes it unresponsive
Date: Sun, 20 May 2007 15:23:55 +0200	[thread overview]
Message-ID: <200705201523.55981.rjw@sisk.pl> (raw)
In-Reply-To: <m3hcq7k5ss.fsf@maximus.localdomain>

On Sunday, 20 May 2007 15:01, Krzysztof Halasa wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
> 
> > Running 'make -j' kernel compilation on my test box (Athlon64 X2, 2 SATA
> > drives
> > with 6 software RAID1 ext3 and reiserfs partitions, 2 GB of RAM) makes it
> > completely unresponsive.  I can't even move the mouse pointer when it's
> > running, I can't log to the box from the network etc.
> 
> How many processes does it spawn? Try some sane limit.

Do you think it works as a fork bomb?  Well, it didn't work like that before,
AFAIR, but then 2.6.21 also does it with the same settings, so sorry for the
noise.

Greetings,
Rafael

  reply	other threads:[~2007-05-20 13:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19  5:17 Linux 2.6.22-rc2 Linus Torvalds
2007-05-19  6:54 ` Andrey Borzenkov
2007-05-19 14:28 ` [BUG: 2.6.22-rc2] SLAB doesn't like usb_get_configuration() Indan Zupancic
     [not found]   ` <6101e8c40705190950jb093d65l611995895a182ec0@mail.gmail.com>
2007-05-19 16:51     ` Fwd: " oliver pinter
2007-05-19 18:20   ` Christoph Lameter
2007-05-19 19:33     ` Greg KH
2007-05-19 22:10       ` Indan Zupancic
2007-05-20 12:57 ` Linux 2.6.22-rc2: make -j makes it unresponsive Rafael J. Wysocki
2007-05-20 13:01   ` Krzysztof Halasa
2007-05-20 13:23     ` Rafael J. Wysocki [this message]
2007-05-20 21:05 ` Linux 2.6.22-rc2 Mike Houston
2007-05-21 15:45   ` Stephen Hemminger
2007-05-21 17:10     ` Mike Houston
2007-05-21 17:37       ` Stephen Hemminger
2007-05-22  2:58         ` Mike Houston
2007-05-22  4:31           ` Stephen Hemminger
2007-05-22  4:36             ` Jeff Garzik
2007-05-22  4:42               ` Stephen Hemminger
2007-05-22  5:04                 ` Linus Torvalds
2007-05-22 17:19                   ` Stephen Hemminger
2007-05-22 17:54                   ` H. Peter Anvin
2007-05-22 22:14             ` Mike Houston
2007-05-23  0:00               ` Linus Torvalds
2007-05-23  0:29                 ` Stephen Hemminger
2007-05-23  1:53                   ` Linus Torvalds
2007-05-23 14:58                     ` Stephen Hemminger
2007-05-23 17:39                 ` Mike Houston
2007-05-23 17:46                   ` Linus Torvalds
2007-05-23 18:04                     ` Stephen Hemminger
2007-05-24 18:26                     ` Mike Houston
2007-05-24 22:08                       ` sky2/pci issues on Gigabyte Stephen Hemminger
2007-05-24 22:48                         ` Linus Torvalds
2007-05-24 23:04                           ` Stephen Hemminger
2007-05-25  0:01                             ` Mike Houston

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=200705201523.55981.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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