Date: Fri, 8 Aug 2008 20:21:41 +0300
From: Adrian Bunk <bunk@kernel.org>
To: Thomas Meyer <thomas@m3y3r.de>, David Howells <dhowells@redhat.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
       Linux-Next <linux-next@vger.kernel.org>
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable
Message-ID: <20080808172141.GY14495@cs181140183.pp.htv.fi>
References: <1218214935.3146.5.camel@dhcppc0>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <1218214935.3146.5.camel@dhcppc0>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1079
Lines: 36

On Fri, Aug 08, 2008 at 07:02:15PM +0200, 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?

The only commits that touched kernel/fork.c between next-20080807 and 
next-20080808 are David's CRED patches.

David, can you look at this?

> with kind regards
> thomas

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/