From: Andrew Morton <akpm@osdl.org>
To: J M Cerqueira Esteves <jmce@artenumerica.com>
Cc: linux-kernel@vger.kernel.org, support@artenumerica.com
Subject: Re: oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T
Date: Thu, 2 Mar 2006 01:17:35 -0800 [thread overview]
Message-ID: <20060302011735.55851ca2.akpm@osdl.org> (raw)
In-Reply-To: <4405D383.5070201@artenumerica.com>
J M Cerqueira Esteves <jmce@artenumerica.com> wrote:
>
> On a dual EM64T Xeon with 4GB of RAM, I am getting apparently "innocent"
> processes killed by oom-killer with gfp_mask=0xd1 (with all or almost
> all swap space still available).
>
That's quite an old kernel. If this is the notorious bio-uses-GFP_DMA bug
then I'd have expected this kernel to be useless from day one. Did you
install it recently?
> I haven't tried 2.6.15 kernels yet, but according to recent reports in
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175173
> even those may still have oom-killer problems (like this?).
Yes, I expect it's the same still-unfixed bug.
If you're feeling keen you could add this patch which would confirm it:
--- devel/mm/oom_kill.c~a 2006-03-02 01:16:17.000000000 -0800
+++ devel-akpm/mm/oom_kill.c 2006-03-02 01:16:32.000000000 -0800
@@ -258,6 +258,8 @@ void out_of_memory(unsigned int __nocast
struct mm_struct *mm = NULL;
task_t * p;
+ dump_stack();
+
read_lock(&tasklist_lock);
retry:
p = select_bad_process();
_
And if it's that bug then I'm afraid you'll have to sit tight until 2.6.16.
We shouldn't release 2.6.16 until this thing is fixed.
next prev parent reply other threads:[~2006-03-02 9:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 17:01 oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T J M Cerqueira Esteves
2006-03-02 9:17 ` Andrew Morton [this message]
2006-03-03 15:50 ` J M Cerqueira Esteves
2006-03-04 15:57 ` oom-killer: gfp_mask=0xd1 with 2.6.15.4 on EM64T [previously 2.6.12] J M Cerqueira Esteves
2006-03-05 0:15 ` Andrew Morton
2006-03-05 2:55 ` J M Cerqueira Esteves
2006-03-05 10:07 ` J M Cerqueira Esteves
2006-03-06 8:47 ` J M Cerqueira Esteves
2006-03-06 9:02 ` Andrew Morton
2006-03-06 18:03 ` Jun'ichi Nomura
2006-03-17 9:47 ` J M Cerqueira Esteves
2006-03-06 9:19 ` J M Cerqueira Esteves
2006-03-06 9:28 ` Andrew Morton
2006-03-06 10:45 ` J M Cerqueira Esteves
2006-03-06 15:56 ` Randy.Dunlap
2006-03-05 0:12 ` oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T Andrew Morton
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=20060302011735.55851ca2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jmce@artenumerica.com \
--cc=linux-kernel@vger.kernel.org \
--cc=support@artenumerica.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