linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: dave b <db.pub.mail@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: David Rientjes <rientjes@google.com>,
	Hugh Dickins <hughd@google.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels
Date: Tue, 27 Jul 2010 18:09:41 +1000	[thread overview]
Message-ID: <AANLkTikjJ0giM+MpzNu3e0NQN=JLMviPT8UPHdZqGGpz@mail.gmail.com> (raw)
In-Reply-To: <20100727150138.2F20.A69D9226@jp.fujitsu.com>

On 27 July 2010 16:09, KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>> > Do you mean the issue will be gone if disabling intel graphics?
>> It may be a general issue or it could just be specific :)
>
> Hmm.. I'm puzzled 8-)
>
> I don't understand why other all people can't reproduce your issue
> even though your reproduce program is very simple.
>
> So, I'm guessing there is hidden reproduce condition. but I have no
> idea to find it.

I will try with the latest ubuntu and report how that goes (that will
be using fairly new xorg etc.) it is likely to be hidden issue just
with the intel graphics driver. However, my concern is that it isn't -
and it is about how shared graphics memory is handled :)

--
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>

  reply	other threads:[~2010-07-27  8:09 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: " 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
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 [this message]
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='AANLkTikjJ0giM+MpzNu3e0NQN=JLMviPT8UPHdZqGGpz@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