From: Raymond Jennings <shentino@gmail.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: Jonathan Woithe <jwoithe@atrad.com.au>,
David Rientjes <rientjes@google.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: OOM triggered with plenty of memory free
Date: Sat, 16 Mar 2013 02:33:23 -0700 [thread overview]
Message-ID: <CAGDaZ_ryxdMBm44kotjKyCeFEFk3OURjHav3zVOcQNGwP_ZwAQ@mail.gmail.com> (raw)
In-Reply-To: <CAJd=RBDHwgtm=to3WUj73d7q6cjJ7oG6capjUxvcpVk0wH-fbQ@mail.gmail.com>
On Sat, Mar 16, 2013 at 2:25 AM, Hillf Danton <dhillf@gmail.com> wrote:
>> Some system specifications:
>> - CPU: i7 860 at 2.8 GHz
>> - Mainboard: Advantech AIMB-780
>> - RAM: 4 GB
>> - Kernel: 2.6.35.11 SMP, 32 bit (kernel.org kernel, no patches applied)
> The highmem no longer holds memory with 64-bit kernel.
I don't really think that's a valid reason to dismiss problems with
32-bit though, as I still use it myself.
Anyway, to the parent poster, could you tell us more, such as how much
ram you had left free?
A printout of /proc/meminfo might help here.
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-03-16 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 9:25 Hillf Danton
2013-03-16 9:33 ` Raymond Jennings [this message]
2013-03-16 11:02 ` Jonathan Woithe
2013-03-20 5:47 ` Jonathan Woithe
2013-03-21 7:07 ` Jonathan Woithe
2013-03-25 2:24 ` Jonathan Woithe
-- strict thread matches above, loose matches on Subject: below --
2013-02-13 3:10 Jonathan Woithe
2013-02-13 3:30 ` David Rientjes
2013-02-13 4:25 ` Jonathan Woithe
2013-02-13 15:14 ` Dave Hansen
2013-02-13 22:49 ` Jonathan Woithe
2013-02-21 6:01 ` Jonathan Woithe
2013-02-26 6:39 ` Jonathan Woithe
2013-02-26 15:26 ` Dave Hansen
2013-02-26 20:54 ` Eric W. Biederman
2013-03-04 5:25 ` Jonathan Woithe
2013-02-20 5:50 ` Simon Jeons
2013-02-20 7:05 ` David Rientjes
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=CAGDaZ_ryxdMBm44kotjKyCeFEFk3OURjHav3zVOcQNGwP_ZwAQ@mail.gmail.com \
--to=shentino@gmail.com \
--cc=dhillf@gmail.com \
--cc=jwoithe@atrad.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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