From: William Thompson <wt@electro-mechanical.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: OOM help
Date: Thu, 28 Oct 2010 08:12:40 -0400 [thread overview]
Message-ID: <20101028121240.GA14603@electro-mechanical.com> (raw)
In-Reply-To: <20100916164231.3BC3.A69D9226@jp.fujitsu.com>
On Fri, Sep 17, 2010 at 09:39:11AM +0900, KOSAKI Motohiro wrote:
> Hi William
>
> That said, there are two possibility.
> 1) your kernel (probably drivers) have memory leak
> 2) you are using really lots of GFP_KERNEL memory. and then, you need to switch 64bit kernel
>
>
> Can you please try latest kernel and try reproduce? I'm curios two point.
> 1) If latest doesn't OOM, the leak has been fixed already. 2) If the OOM occur,
> latest output more detailed information.
>
> But, if you want asap solution, I recommend to try 64bit kernel.
I'm having the problem again. This time, I'm using 2.6.35.4. Would
changing from 1gb kernel/3gb user to 2gb/2gb help? I don't believe I
actually use more than 1gb or so of user space memory anyway.
64-bit would require that I completely reinstall this system which is
definately not something I want to do.
--
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>
prev parent reply other threads:[~2010-10-28 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100915120349.GH29041@electro-mechanical.com>
2010-09-17 0:39 ` OOM help KOSAKI Motohiro
2010-09-17 17:54 ` William Thompson
2010-10-28 12:12 ` William Thompson [this message]
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=20101028121240.GA14603@electro-mechanical.com \
--to=wt@electro-mechanical.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).