From: dave b <db.pub.mail@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels
Date: Tue, 27 Jul 2010 14:39:48 +1000 [thread overview]
Message-ID: <AANLkTi=Aswf+Hp+qfsC2sCo32hU3E2D4zt3-R35BZ=MC@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1007261510320.2993@chino.kir.corp.google.com>
On 27 July 2010 08:12, David Rientjes <rientjes@google.com> wrote:
> On Tue, 27 Jul 2010, dave b wrote:
>
>> Actually it turns out on 2.6.34.1 I can trigger this issue. What it
>> really is, is that linux doesn't invoke the oom killer when it should
>> and kill something off. This is *really* annoying.
>>
>
> I'm not exactly sure what you're referring to, it's been two months and
> you're using a new kernel and now you're saying that the oom killer isn't
> being utilized when the original problem statement was that it was killing
> things inappropriately?
Sorry about the timespan :(
Well actually it is the same issue. Originally the oom killer wasn't
being invoked and now the problem is still it isn't invoked - it
doesn't come and kill things - my desktop just sits :)
I have since replaced the hard disk - which I thought could be the
issue. I am thinking that because I have shared graphics not using KMS
- with intel graphics - this may be the root of the cause.
--
All things that are, are with more spirit chased than enjoyed. --
Shakespeare, "Merchant of Venice"
--
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:[~2010-07-27 4:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimAF1zxXlnEavXSnlKTkQgGD0u9UqCtUVT_r9jV@mail.gmail.com>
[not found] ` <AANLkTimUYmUCdFMIaVi1qqcz2DqGoILeu43XWZBHSILP@mail.gmail.com>
[not found] ` <AANLkTikTYbPKTaEMbdwGikV1Og4VQtXUCgNq0EldbR4U@mail.gmail.com>
[not found] ` <AANLkTimJ_ROa55mX9sCs9TkoBZFEze5Ak-LQsAMeeigq@mail.gmail.com>
2010-05-21 5:48 ` Fwd: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels dave b
[not found] ` <AANLkTilmr29Vv3N64n7KVj9fSDpfBHIt8-quxtEwY0_X@mail.gmail.com>
2010-05-21 21:18 ` Hugh Dickins
2010-05-27 3:45 ` dave b
2010-06-01 20:52 ` David Rientjes
2010-07-26 14:05 ` dave b
2010-07-26 22:12 ` David Rientjes
2010-07-27 4:39 ` dave b [this message]
2010-07-27 4:46 ` KOSAKI Motohiro
2010-07-27 4:49 ` dave b
2010-07-27 6:09 ` KOSAKI Motohiro
2010-07-27 8:09 ` dave b
2010-07-27 10:40 ` dave b
2010-07-27 11:14 ` KOSAKI Motohiro
2010-07-27 11:26 ` dave b
2010-07-28 5:06 ` KOSAKI Motohiro
2010-07-28 7:14 ` dave b
2010-07-29 9:47 ` dave b
2010-07-29 9:48 ` dave b
2010-09-21 13:01 ` dave b
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='AANLkTi=Aswf+Hp+qfsC2sCo32hU3E2D4zt3-R35BZ=MC@mail.gmail.com' \
--to=db.pub.mail@gmail.com \
--cc=hughd@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).