From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Mauricio Lin <mauriciolin@gmail.com>
Subject: Re: oom with 2.6.11
Date: Wed, 09 Mar 2005 15:00:10 +0100 [thread overview]
Message-ID: <422F016A.2090107@g-house.de> (raw)
In-Reply-To: <3f250c7105030905415cab5192@mail.gmail.com>
Mauricio Lin wrote:
> Hi Christian,
>
> I found the 2.6.11-rc3 patch. The oom killer modification from
> Arcangeli was included in 2.6.11-rc3. Right? So this is correct, so
> the problem is not related to Arcangeli modification.
>
> Does anyone have idea?
hi Mauricio,
thank you for your answers, but i'm unable to investigate right now, will
do so in the evening.
thanks,
Christian.
--
BOFH excuse #240:
Too many little pins on CPU confusing it, bend back and forth until 10-20%
are neatly removed. Do _not_ leave metal bits visible!
next prev parent reply other threads:[~2005-03-09 14:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 15:21 oom with 2.6.11 Christian Kujau
2005-03-09 13:18 ` Mauricio Lin
2005-03-09 13:41 ` Mauricio Lin
2005-03-09 14:00 ` Christian Kujau [this message]
2005-03-10 15:12 ` Christian Kujau
2005-03-11 0:39 ` Andrew Morton
2005-03-11 1:14 ` Christian Kujau
2005-03-11 7:45 ` Pasi Kärkkäinen
2005-03-11 9:01 ` Mauricio Lin
2005-03-11 15:09 ` Christian Kujau
2005-03-15 8:52 ` Mauricio Lin
2005-03-15 14:12 ` Christian Kujau
2005-03-20 14:35 ` [SOLVED] " Christian Kujau
2005-03-11 10:59 ` Coywolf Qi Hunt
2005-03-11 15:10 ` Christian Kujau
2005-03-12 18:06 ` Christian Kujau
2005-03-17 1:27 ` Christian Kujau
2005-03-17 1:51 ` Andrew Morton
2005-03-17 2:00 ` Christian Kujau
2005-03-17 21:25 ` Coywolf Qi Hunt
2005-03-18 1:59 ` Christian Kujau
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 13:22 OOM " Christian Kujau
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=422F016A.2090107@g-house.de \
--to=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mauriciolin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.