[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080809084621.GA9285@mars.unix.geek.nz>
Date: Sat, 9 Aug 2008 20:46:21 +1200
From: jasper@...ton.co.nz
To: James Morris <jmorris@...ei.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable
On Sat, Aug 09, 2008 at 08:44:17PM +1200, jasper@...ton.co.nz wrote:
> On Sat, Aug 09, 2008 at 07:48:05AM +1000, James Morris wrote:
> > 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.
>
> This is occurring for me too, fresh git checkout of next-20080808.
> .config attached.
>
> Interestingly if I start X, fork() works for a bit - long enough for me
> to get a terminal open and type a command or two - but then all commands
> start returning the above error (except with zsh, not bash).
>
> If I then switch to VT1 I can use the console fine.
Sorry, wrong .config :|
Correct one attached.
-jasper
View attachment ".config" of type "text/plain" (60626 bytes)
Powered by blists - more mailing lists