From: dave b <db.pub.mail@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels
Date: Thu, 20 May 2010 17:27:10 +1000 [thread overview]
Message-ID: <AANLkTilmr29Vv3N64n7KVj9fSDpfBHIt8-quxtEwY0_X@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimUYmUCdFMIaVi1qqcz2DqGoILeu43XWZBHSILP@mail.gmail.com>
Is there a reason - no one has taken any interesting in my email ?....
The behaviour isn't found on the 2.6.26 debian kernel. So I was
thinking that it might be due to my intel graphics card / memory
interplay ? ....
On 14 May 2010 23:14, dave b <db.pub.mail@gmail.com> wrote:
> On 14 May 2010 22:53, dave b <db.pub.mail@gmail.com> wrote:
>> In 2.6.3* kernels (test case was performed on the 2.6.33.3 kernel)
>> when physical memory runs out and there is a large swap partition -
>> the system completely stalls.
>>
>> I noticed that when running debian lenny using dm-crypt with
>> encrypted / and swap with a 2.6.33.3 kernel (and all of the 2.6.3*
>> series iirc) when all physical memory is used (swapiness was left at
>> the default 60) the system hangs and does not respond. It can resume
>> normal operation some time later - however it seems to take a *very*
>> long time for the oom killer to come in. Obviously with swapoff this
>> doesn't happen - the oom killer comes in and does its job.
>>
>>
>> free -m
>> total used free shared buffers cached
>> Mem: 1980 1101 879 0 58 201
>> -/+ buffers/cache: 840 1139
>> Swap: 24943 0 24943
>>
>>
>> My simple test case is
>>
>> dd if=/dev/zero of=/tmp/stall
>> and wait till /tmp fills...
>>
>
> Sorry - I forgot to say I am running x86-64
>
next prev parent reply other threads:[~2010-05-20 7:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 12:53 PROBLEM: oom killer and swap weirdness on 2.6.3* kernels dave b
2010-05-14 13:14 ` dave b
2010-05-20 7:27 ` dave b [this message]
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
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=AANLkTilmr29Vv3N64n7KVj9fSDpfBHIt8-quxtEwY0_X@mail.gmail.com \
--to=db.pub.mail@gmail.com \
--cc=linux-kernel@vger.kernel.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).