From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: kosaki.motohiro@jp.fujitsu.com, Roman Jarosz <kedgedev@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
A Rojas <nqn1976list@gmail.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
"A. Boulan" <arnaud.boulan@libertysurf.fr>,
michael@reinelt.co.at, jcnengel@googlemail.com,
rientjes@google.com, earny@net4u.de,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Eric Anholt <eric@anholt.net>
Subject: Re: OOM-Killer kills too much with 2.6.32.2
Date: Wed, 27 Jan 2010 09:50:32 +0900 (JST) [thread overview]
Message-ID: <20100127091903.6AD5.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <89khjo$egh4fr@orsmga002.jf.intel.com>
> On Tue, 26 Jan 2010 22:03:06 +0900, KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> > Please consider to revert such commit at once. Lots people reported
> > the same issue.
> > I really hope to stop bug report storm.
>
> Your CC did not reference the problem that you were discussing, nor that
> it is even easier to trigger an OOM without the shrinker. Memory
> exhaustion due to the excess usage of surfaces from userspace is not a new
> issuer. So what is the problem you have encountered and how does running
> the OOM killer earlier fix the issue of triggering the OOM killer?
Why do you bother easy googling?
example.
1) http://bugzilla.kernel.org/show_bug.cgi?id=14933
Subject : OOM killer unexpectedly called with kernel 2.6.32
Submitter : "A. Boulan" <arnaud.boulan@libertysurf.fr>
Date : 2009-12-24 23:42
References : http://marc.info/?l=linux-kernel&m=126169821317492&w=4
2) http://bugzilla.kernel.org/show_bug.cgi?id=15015
Subject: blank screen at random times in laptop when sitting idle
From: Jithin Emmanuel
Date: 2010-01-09 16:48:23
see comment #2
3) http://bugzilla.kernel.org/show_bug.cgi?id=15058
From: Michael Reinelt
Date: 2010-01-14 16:39:51
4) Subject: Re: OOM kernel behaviour
From: David John <davidjon@xenontk.org>
Mon, 07 Dec 2009 11:04:24 +0530
5) This thread
next prev parent reply other threads:[~2010-01-27 0:50 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 13:15 Roman Jarosz
2010-01-23 0:40 ` David Rientjes
2010-01-25 22:12 ` Roman Jarosz
2010-01-25 1:48 ` KOSAKI Motohiro
2010-01-25 20:47 ` Roman Jarosz
2010-01-26 5:19 ` KOSAKI Motohiro
2010-01-26 7:51 ` A Rojas
2010-01-26 9:06 ` Roman Jarosz
2010-01-26 11:07 ` KOSAKI Motohiro
2010-01-26 12:33 ` Chris Wilson
2010-01-26 13:03 ` KOSAKI Motohiro
2010-01-26 13:18 ` Chris Wilson
2010-01-26 13:59 ` Michael Reinelt
2010-01-26 14:07 ` Michael Reinelt
2010-01-27 0:50 ` KOSAKI Motohiro [this message]
2010-01-27 9:56 ` Pekka Enberg
2010-01-27 10:55 ` Linus Torvalds
2010-01-27 11:12 ` Pekka Enberg
2010-01-27 11:14 ` [PATCH] drm/i915: Selectively enable self-reclaim Chris Wilson
2010-01-27 11:20 ` Pekka Enberg
2010-01-27 11:30 ` Michael Reinelt
2010-01-28 3:15 ` Michael Reinelt
2010-01-28 18:21 ` Roman Jarosz
2010-01-27 11:50 ` KOSAKI Motohiro
2010-01-27 12:16 ` Linus Torvalds
2010-01-27 12:28 ` Linus Torvalds
2010-01-27 15:25 ` Chris Wilson
2010-01-27 16:09 ` Linus Torvalds
2010-01-27 17:14 ` Chris Wilson
2010-01-27 17:19 ` Linus Torvalds
2010-01-27 21:03 ` Roman Jarosz
2010-06-30 6:54 ` [Intel-gfx] " Dave Airlie
2010-06-30 7:05 ` Chris Wilson
2010-06-30 23:07 ` Linus Torvalds
2010-07-01 1:24 ` Linus Torvalds
2010-07-01 1:55 ` KOSAKI Motohiro
2010-07-01 10:15 ` Dave Airlie
2010-07-01 11:19 ` Chris Wilson
2010-07-01 22:34 ` M. Vefa Bicakci
2010-07-01 23:59 ` Linus Torvalds
2010-07-02 0:06 ` Dave Airlie
2010-07-02 0:49 ` Dave Airlie
2010-07-02 1:28 ` Linus Torvalds
2010-07-17 18:58 ` M. Vefa Bicakci
2010-07-17 19:15 ` Linus Torvalds
2010-07-18 14:27 ` M. Vefa Bicakci
2010-07-18 16:59 ` Linus Torvalds
2010-01-28 6:37 ` Willy Tarreau
2010-01-26 13:41 ` OOM-Killer kills too much with 2.6.32.2 Roman Jarosz
2010-01-27 0:14 ` KOSAKI Motohiro
2010-01-27 9:53 ` Roman Jarosz
2010-01-26 13:57 ` Pekka Enberg
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=20100127091903.6AD5.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=arnaud.boulan@libertysurf.fr \
--cc=chris@chris-wilson.co.uk \
--cc=earny@net4u.de \
--cc=eric@anholt.net \
--cc=hugh.dickins@tiscali.co.uk \
--cc=jbarnes@virtuousgeek.org \
--cc=jcnengel@googlemail.com \
--cc=kedgedev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@reinelt.co.at \
--cc=nqn1976list@gmail.com \
--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
Powered by JetHome