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: Thu, 29 Jul 2010 19:48:14 +1000 [thread overview]
Message-ID: <AANLkTikN7XN3hymsmqH05nynAHH9st0W2pkDhoCLUTo9@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikq=v_7dbW1Z+LUbTKmnezKT0cd8ZTErwP1X0C+@mail.gmail.com>
On 29 July 2010 19:47, dave b <db.pub.mail@gmail.com> wrote:
> On 28 July 2010 17:14, dave b <db.pub.mail@gmail.com> wrote:
>> On 28 July 2010 15:06, KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>>>> On 27 July 2010 21:14, KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>>>> >> On 27 July 2010 18:09, dave b <db.pub.mail@gmail.com> wrote:
>>>> >> > 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 :)
>>>> >> >
>>>> >> > 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 :)
>>>> >>
>>>> >>
>>>> >> Ok my desktop still stalled and no oom killer was invoked when I added
>>>> >> swap to a live-cd of 10.04 amd64.
>>>> >>
>>>> >> *Without* *swap* *on* - the oom killer was invoked - here is a copy of it.
>>>> >
>>>> > This stack seems similar following bug. can you please try to disable intel graphics
>>>> > driver?
>>>> >
>>>> > https://bugzilla.kernel.org/show_bug.cgi?id=14933
>>>>
>>>> Ok I am not sure how to do that :)
>>>> I could revert the patch and see if it 'fixes' this :)
>>>
>>> Oops, no, revert is not good action. the patch is correct.
>>> probably my explanation was not clear. sorry.
>>>
>>> I did hope to disable 'driver' (i.e. using vga), not disable the patch.
>>
>> Oh you mean in xorg, I will also blacklist the module. Sure that patch
>> might not it but in 2.6.26 the problem isn't there :)
>
> Ok I re-tested with 2.6.26 and 2.6.34.1
> So I will describe what happens below:
>
> 2.6.26 - with xorg running
> "Given I have a test file called a.out
> And I can see Xorg
> And I am using 2.6.26
> And I have swap on
> When I run it I run a.out
> Then I see the system freeze up slightly
> And the hard drive churns( and the cpu is doing something as the
> large fan kicks)
> And after a while the system unfreezes"
>
> 2.6.26 - from single mode - before xorg starts and i915 is *not* loaded.
> "Given I have a test file called a.out
> And I cannot see Xorg
> And I am using 2.6.26
> And I have swap on
> When I run it I run a.out
> Then I see the system freeze up
> And the system fan doesn't spin any faster
> And the system just sits idle"
>
> 2.6.34.1
> With and without xorg - WITH spam on the same behaviour as in the
> 2.6.26 kernel appears (when xorg is not loaded).
>
> OOM attached from the 2.6.26 kernel when I used magic keys to invoke
> the oom killer :) (this was on the 2.6.26 kernel - before i915 had
> loaded and in single mode).
s/spam/same/
--
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-29 9:48 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
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 [this message]
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=AANLkTikN7XN3hymsmqH05nynAHH9st0W2pkDhoCLUTo9@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).