From: mark <markkicks@gmail.com>
To: "Randy Dunlap" <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fork: Resource temporarily unavailable / cant start new threads
Date: Wed, 21 May 2008 17:09:01 -0700 [thread overview]
Message-ID: <82fa9e310805211709i3993cac2n58152cf11a3ef8a4@mail.gmail.com> (raw)
In-Reply-To: <20080521163503.000afd61.randy.dunlap@oracle.com>
On Wed, May 21, 2008 at 4:35 PM, Randy Dunlap <randy.dunlap@oracle.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@localhost 2.6.25.3-18.fc9.i686]$ find . -iname '*fork*' -print
[mark@localhost 2.6.25.3-18.fc9.i686]$ rpm -ql
[mark@localhost 2.6.25.3-18.fc9.i686]$ rpm -ql kernel-devel | grep fork
[mark@localhost 2.6.25.3-18.fc9.i686]$ pwd
/usr/src/kernels/2.6.25.3-18.fc9.i686
next prev parent reply other threads:[~2008-05-22 0:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 18:26 mark
2008-05-21 20:28 ` Randy Dunlap
2008-05-21 20:39 ` mark
2008-05-21 20:50 ` Randy Dunlap
2008-05-21 21:08 ` mark
2008-05-21 21:15 ` Jesper Juhl
2008-05-21 21:27 ` mark
2008-05-21 21:32 ` Randy Dunlap
2008-05-21 22:51 ` mark
2008-05-21 23:35 ` Randy Dunlap
2008-05-22 0:09 ` mark [this message]
2008-05-22 0:29 ` Randy Dunlap
2008-05-22 7:11 ` するくめ
2008-05-21 20:39 ` Johannes Weiner
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=82fa9e310805211709i3993cac2n58152cf11a3ef8a4@mail.gmail.com \
--to=markkicks@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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
all inboxes | Powered by JetHome®