[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82fa9e310805211709i3993cac2n58152cf11a3ef8a4@mail.gmail.com>
Date: Wed, 21 May 2008 17:09:01 -0700
From: mark <markkicks@...il.com>
To: "Randy Dunlap" <randy.dunlap@...cle.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: fork: Resource temporarily unavailable / cant start new threads
On Wed, May 21, 2008 at 4:35 PM, Randy Dunlap <randy.dunlap@...cle.com> wrote:
>> > I can send you some debug patches that will print out the specific
>> > problem area. Do you want to do that? Can you rebuild and install
>> > a new kernel?
>> Is it possible to get this debug messages by turning on some flags?
>> If not yes, pl. send debug patches. its a live box and I will try to do it!
>>
>> This is my system / kernel info:
>> uname -a
>> Linux XXX 2.6.25.3-18.fc9.x86_64 #1 SMP Tue May 13 04:54:47 EDT 2008
>> x86_64 x86_64 x86_64 GNU/Linux
>
> I made a small patch to a vanilla kernel.org 2.6.25.3 kernel tree.
> Hopefully it applies cleanly to that fc9 kernel source, but check/verify
> that first before going any further.
Thanks a lot for the patch,
This is kind of weird.. but there is no file kernel/fork.c
[mark@...alhost 2.6.25.3-18.fc9.i686]$ find . -iname '*fork*' -print
[mark@...alhost 2.6.25.3-18.fc9.i686]$ rpm -ql
[mark@...alhost 2.6.25.3-18.fc9.i686]$ rpm -ql kernel-devel | grep fork
[mark@...alhost 2.6.25.3-18.fc9.i686]$ pwd
/usr/src/kernels/2.6.25.3-18.fc9.i686
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists