public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: dhowells@redhat.com, James Morris <jmorris@namei.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Linux-Next <linux-next@vger.kernel.org>
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable
Date: Sat, 09 Aug 2008 13:52:07 +0100	[thread overview]
Message-ID: <14476.1218286327@redhat.com> (raw)
In-Reply-To: <1218281190.3155.5.camel@dhcppc0>

Thomas Meyer <thomas@m3y3r.de> wrote:

> > > Beginning with next-20080808 after letting the system run for 5 minutes
> > > or so, I get an error from the fork call, e.g.:
> > > 
> > > "bash: fork: Resource temporarily unavailable"

I modified your config slightly so that it'd run on my testbox (x86_64
unfortunately), but that survived LTP and seemed to work okay.  I'll have to
snag an i386 installation from somewhere, unless James can do me a favour and
test it on his, if he has one.

Can you try this please:

	cat /proc/slabinfo  | cut -d: -f1 | sort -k 2 -n

Just to check to see if there's a memory leak.

Interestingly, I notice that SLUB's /proc/slabinfo appears to be broken.  It's
missing a number of slab caches from the list.

David

  reply	other threads:[~2008-08-09 12:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 17:02 next-20080808: bash: fork: Resource temporarily unavailable Thomas Meyer
2008-08-08 17:21 ` Adrian Bunk
2008-08-08 22:32   ` David Howells
2008-08-08 22:48     ` James Morris
2008-08-08 23:23       ` David Howells
2008-08-08 21:48 ` James Morris
2008-08-09  8:44   ` jasper
2008-08-09  8:46     ` jasper
2008-08-09 11:26   ` Thomas Meyer
2008-08-09 12:52     ` David Howells [this message]
2008-08-09 13:11       ` Thomas Meyer
2008-08-09 14:07         ` David Howells
2008-08-09 22:55           ` Jasper Bryant-Greene
2008-08-10  9:45             ` David Howells
2008-08-10 10:30               ` Grant Wilson
2008-08-10 11:31                 ` David Howells
2008-08-11  0:26                   ` James Morris
2008-08-11  0:21                 ` David Howells
2008-08-11  0:44                   ` James Morris

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=14476.1218286327@redhat.com \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    /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