From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Miguel Figueiredo <elmig@debianpt.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.21 frozen for a few minutes, swapping to disk
Date: Tue, 01 May 2007 15:42:30 +1000 [thread overview]
Message-ID: <4636D346.2010507@yahoo.com.au> (raw)
In-Reply-To: <20070430003031.2e89fbc1.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sun, 29 Apr 2007 11:28:05 +0100 Miguel Figueiredo <elmig@debianpt.org> wrote:
>
>
>>Hi all,
>>
>>today, with 2.6.21, my laptop had a really odd behaviour. It started
>>writing to disk for a few minutes with no interactivity at all (no
>>redraw on screen, only hdd led on). It's the first time i noticed
>>OOM-killer started do kill programs.
>>
>>It was totally unresponsive for minutes, after back to life it had a
>>load of ~19.0, and 300+ MB on swap (first time i saw this).
>>
>>It's an HP pavillon core duo 2.0 GHz, 1 GB RAM
>>
>>kern.log details:
>>http://www.debianpt.org/~elmig/pool/kernel/20070429/kern.log
>>.config: http://www.debianpt.org/~elmig/pool/kernel/20070429/2.6.21.config
>>dmesg: http://www.debianpt.org/~elmig/pool/kernel/20070429/dmesg
>>
>>As this is the first time it happened and it felt odd i am reporting.
>>
>>If aditional info is needed please CC me as i am not on the list.
>>
>
>
> hm, a genuine oom on an all-ext3 data=ordered i386 system, just like a
> million other people. How very weird.
>
> I assume all those pages on the LRU are pagecache pages which for some
> reason we're unable to reclaim.
It looks like it used up all swap? I'd guess a memory leak in some
application, or maybe a page refcount leak somewhere.
>
> If some privileged application went berzerk mlock()ing everything then that
> might explain it. It sounds improbable, but then, something improbable has
> happened.
>
> We cleverly managed to not display the pagecache totals in the oom-killer
> output. Could you please take a copy of /proc/meminfo after an
> oom-killing, send that? And /proc/vmstat, I guess.
>
> If you're keen, we could eliminate the mlock possibility by adding this:
>
> --- a/mm/mlock.c~a
> +++ a/mm/mlock.c
> @@ -127,6 +127,8 @@ asmlinkage long sys_mlock(unsigned long
> unsigned long lock_limit;
> int error = -ENOMEM;
>
> + return 0;
> +
> if (!can_do_mlock())
> return -EPERM;
>
> @@ -151,6 +153,8 @@ asmlinkage long sys_munlock(unsigned lon
> {
> int ret;
>
> + return 0;
> +
> down_write(¤t->mm->mmap_sem);
> len = PAGE_ALIGN(len + (start & ~PAGE_MASK));
> start &= PAGE_MASK;
> _
>
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-05-01 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 10:28 2.6.21 frozen for a few minutes, swapping to disk Miguel Figueiredo
2007-04-30 7:30 ` Andrew Morton
2007-05-01 5:42 ` Nick Piggin [this message]
2007-05-01 5:49 ` Andrew Morton
2007-05-01 5:58 ` Nick Piggin
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=4636D346.2010507@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=elmig@debianpt.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.