From: James Morris <jmorris@namei•org>
To: Thomas Meyer <thomas@m3y3r•de>
Cc: Linux-Kernel <linux-kernel@vger•kernel.org>,
Linux-Next <linux-next@vger•kernel.org>,
David Howells <dhowells@redhat•com>
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable
Date: Sat, 9 Aug 2008 07:48:05 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.1.10.0808090747150.29079@tundra.namei.org> (raw)
In-Reply-To: <1218214935.3146.5.camel@dhcppc0>
On Fri, 8 Aug 2008, Thomas Meyer wrote:
> Hi.
>
> 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"
>
> Doing an "echo c > /proc/sysrq-trigger" I was able to get an vmcore dump
> of the running kernel using the kdump mechanism.
>
> what should i do next?
Which distro and version are you using? Please post your .config file.
--
James Morris
<jmorris@namei•org>
next prev parent reply other threads:[~2008-08-08 21:48 UTC|newest]
Thread overview: 17+ 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 [this message]
2008-08-09 11:26 ` Thomas Meyer
2008-08-09 12:52 ` David Howells
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=alpine.LRH.1.10.0808090747150.29079@tundra.namei.org \
--to=jmorris@namei$(echo .)org \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=thomas@m3y3r$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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