From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Coywolf Qi Hunt <coywolf@gmail.com>
Subject: Re: oom with 2.6.11
Date: Fri, 11 Mar 2005 16:10:33 +0100 [thread overview]
Message-ID: <4231B4E9.3080005@g-house.de> (raw)
In-Reply-To: <2cd57c9005031102595dfe78e6@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Coywolf Qi Hunt wrote:
> In file mm/oom_kill.c, uncomment line 24: /* #define DEBUG */.
> And next time when oom happens again, we'll see the badness.
oh, good hint. will do this before the next reboot (in a few hours i guess)
thanks,
Christian.
- --
BOFH excuse #134:
because of network lag due to too many people playing deathmatch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCMbTj+A7rjkF8z0wRAmdAAJ4sCIaUqZaKn7gGtkpN7Wb47acFiACgrOSe
DpT3tE1/4zfPIDueDwBMhDU=
=o6Lr
-----END PGP SIGNATURE-----
--
BOFH excuse #37:
heavy gravity fluctuation, move computer to floor rapidly
next prev parent reply other threads:[~2005-03-11 15:13 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
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 [this message]
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=4231B4E9.3080005@g-house.de \
--to=evil@g-house.de \
--cc=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.