From: Justin Mattock <justinmattock@gmail.com>
To: Jiri Slaby <jirislaby@gmail.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: Mon, 2 Nov 2009 14:02:14 -0800 [thread overview]
Message-ID: <dd18b0c30911021402t6c8b9cd4p2e5d5dcad732d0ac@mail.gmail.com> (raw)
In-Reply-To: <4AEF53F5.4020107@gmail.com>
On Mon, Nov 2, 2009 at 1:49 PM, Jiri Slaby <jirislaby@gmail.com> wrote:
> On 11/02/2009 10:29 PM, Justin Mattock wrote:
>> [ 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.957951] Out of memory: kill process 16001 (c++) score 543727 or a child
>> [ 532.957955] Killed process 16002 (cc1plus)
>>
>> I just compiled the latest gcc snapshot a few days
>> ago.
>
> How many jobs did you run in parallel? Was there anything else memory
> consuming running on that machine? Do you run the same jobs count every
> time you compile such big c++ projects?
>
This would be the only job running.
as for other types of jobs under ps aux there's only
udev,dbus,acpid,sshd,wicd running.
Now with this oom-killer I'm
hitting this on an imac9,1 with
gcc (GCC) 4.5.0 20091029 (experimental)
2.6.32-rc5-00083-g04ea458
On my other machine macbook pro ati chipset
(same system pure64)firefox seems to be going a lot farther
than on the imac(doing this in the past I think this takes a good
45min to compile).
the macbook has:
gcc (GCC) Cross-LFS 4.4.1.20090722) 4.4.1
2.6.32-rc4-00039-ga3f6f2e
--
Justin P. Mattock
next prev parent reply other threads:[~2009-11-02 22:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 21:29 Justin Mattock
2009-11-02 21:49 ` Jiri Slaby
2009-11-02 22:02 ` Justin Mattock [this message]
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
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=dd18b0c30911021402t6c8b9cd4p2e5d5dcad732d0ac@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jirislaby@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 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®