From: "Justin P. Mattock" <justinmattock@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
gcc@gcc.gnu.org
Subject: Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
Date: Tue, 03 Nov 2009 17:40:20 -0800 [thread overview]
Message-ID: <4AF0DB84.8050006@gmail.com> (raw)
In-Reply-To: <20091104101410.D43E.A69D9226@jp.fujitsu.com>
KOSAKI Motohiro wrote:
>> Hello,
>> I'm not sure how to handle this,
>> while compiling firefox-3.6b1.source
>> I get this with the default compiling options,
>> as well as custom:
>>
>>
>> [ 532.942324] cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
>> [ 532.942330] Pid: 16002, comm: cc1plus Tainted: P
>> 2.6.32-rc5-00083-g04ea458 #2
>> [ 532.942333] Call Trace:
>> [ 532.942342] [<ffffffff810bce11>] T.417+0x7c/0x245
>> [ 532.942347] [<ffffffff810bd11c>] __out_of_memory+0x142/0x159
>> [ 532.942352] [<ffffffff810bd1a1>] out_of_memory+0x6e/0x9d
>> [ 532.942357] [<ffffffff810c0086>] __alloc_pages_nodemask+0x47e/0x5cc
>> [ 532.942363] [<ffffffff810d2115>] handle_mm_fault+0x25d/0x68e
>> [ 532.942369] [<ffffffff813dfc1d>] do_page_fault+0x2bb/0x2d3
>> [ 532.942373] [<ffffffff813ddb25>] page_fault+0x25/0x30
>> [ 532.942376] Mem-Info:
>> [ 532.942378] DMA per-cpu:
>> [ 532.942380] CPU 0: hi: 0, btch: 1 usd: 0
>> [ 532.942383] CPU 1: hi: 0, btch: 1 usd: 0
>> [ 532.942385] DMA32 per-cpu:
>> [ 532.942388] CPU 0: hi: 186, btch: 31 usd: 94
>> [ 532.942391] CPU 1: hi: 186, btch: 31 usd: 23
>> [ 532.942393] Normal per-cpu:
>> [ 532.942395] CPU 0: hi: 186, btch: 31 usd: 150
>> [ 532.942398] CPU 1: hi: 186, btch: 31 usd: 155
>> [ 532.942404] active_anon:707575 inactive_anon:264673 isolated_anon:0
>> [ 532.942406] active_file:58 inactive_file:33 isolated_file:0
>>
>
> file cache (active_file + inactive_file) was very little. It indicate anyone waste too much memory.
> I doubt you use buggy compiler.
>
>
>
>
hmm... then this is something with firefox then..
In that case I'll continue to build my system with
this compiler.
Although a bit concerned building everything
for the system with a compiler that shows some
memory issue,but if you say its not the compiler,
then I'll carry on with what I'm doing.
(and use an older compiler for firefox).
Justin P. Mattock
next prev parent reply other threads:[~2009-11-04 1:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 21:29 cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0 Justin Mattock
2009-11-02 21:49 ` Jiri Slaby
2009-11-02 22:02 ` Justin Mattock
2009-11-02 22:05 ` Jiri Slaby
2009-11-02 22:12 ` Justin P. Mattock
2009-11-03 0:56 ` Justin P. Mattock
2009-11-04 1:18 ` KOSAKI Motohiro
2009-11-04 1:40 ` Justin P. Mattock [this message]
2009-11-04 6:24 ` Andrew Morton
2009-11-04 6:44 ` Justin P. Mattock
2009-11-04 9:14 ` Jiri Slaby
2009-11-04 9:32 ` KOSAKI Motohiro
2009-11-04 15:28 ` Andrew Morton
2009-11-04 23:20 ` KOSAKI Motohiro
2009-11-04 13:13 ` Dave Korn
2009-11-04 15:08 ` Justin P. Mattock
2009-11-04 15:45 ` Dave Korn
2009-11-04 16:39 ` Justin Mattock
2009-11-04 19:48 ` Dave Korn
2009-11-04 20:39 ` Justin P. Mattock
2009-11-04 21:22 ` Justin Mattock
2009-11-05 0:36 ` Dave Korn
2009-11-05 3:36 ` Justin Mattock
2009-11-05 5:08 ` Dave Korn
2009-11-06 21:21 ` Justin P. Mattock
2009-11-10 2:55 ` Justin P. Mattock
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=4AF0DB84.8050006@gmail.com \
--to=justinmattock@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=kosaki.motohiro@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox