From: Thomas Meyer <thomas@m3y3r.de>
To: David Howells <dhowells@redhat.com>
Cc: 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 15:11:13 +0200 [thread overview]
Message-ID: <1218287473.3155.13.camel@dhcppc0> (raw)
In-Reply-To: <14476.1218286327@redhat.com>
Am Samstag, den 09.08.2008, 13:52 +0100 schrieb David Howells:
> 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.
I'm too lazy to reboot now. But i can give you that from vmcore dump:
crash> kmem -i
PAGES TOTAL PERCENTAGE
TOTAL MEM 1524251 5.8 GB ----
FREE 1343484 5.1 GB 88% of TOTAL MEM
USED 180767 706.1 MB 11% of TOTAL MEM
SHARED 19076 74.5 MB 1% of TOTAL MEM
BUFFERS 3800 14.8 MB 0% of TOTAL MEM
CACHED 108483 423.8 MB 7% of TOTAL MEM
SLAB 6239 24.4 MB 0% of TOTAL MEM
TOTAL HIGH 1343440 5.1 GB 88% of TOTAL MEM
FREE HIGH 0 0 0% of TOTAL HIGH
TOTAL LOW 180811 706.3 MB 11% of TOTAL MEM
FREE LOW 1343484 5.1 GB 743% of TOTAL LOW
TOTAL SWAP 1596751 6.1 GB ----
SWAP USED 0 0 0% of TOTAL SWAP
SWAP FREE 1596751 6.1 GB 100% of TOTAL SWAP
Is that what you wanted to know? Doesn't look like a memory leak for me.
kmem -s doesn't seem to work:
crash> kmem -s
kmem: invalid structure member offset: kmem_cache_objects
FILE: memory.c LINE: 13500 FUNCTION: dump_kmem_cache_slub()
[/usr/bin/crash] error trace: 8085195 => 809f8cf => 80c0d82 => 813b9a0
CACHE NAME OBJSIZE ALLOCATED TOTAL SLABS SSIZE
813b9a0: OFFSET_verify+118
80c0d82: dump_kmem_cache_slub+1033
809f8cf: cmd_kmem+3077
8085195: exec_command+265
kmem: invalid structure member offset: kmem_cache_objects
FILE: memory.c LINE: 13500 FUNCTION: dump_kmem_cache_slub()
next prev parent reply other threads:[~2008-08-09 13:11 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
2008-08-09 13:11 ` Thomas Meyer [this message]
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=1218287473.3155.13.camel@dhcppc0 \
--to=thomas@m3y3r.de \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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