From: Michael Raskin <a1d23ab4@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.19-rc1-mm1+ memory problem
Date: Sun, 26 Nov 2006 00:53:19 +0300 [thread overview]
Message-ID: <4568BB4F.2070701@mail.ru> (raw)
In-Reply-To: <20061125110331.10f2dd42.akpm@osdl.org>
Andrew Morton wrote:
>> 89361 times:
>> Page allocated via order 0, mask 0x280d2
>> [0xc0159f31] __handle_mm_fault+1809
>> [0xc011318a] do_page_fault+314
>> [0xc04111c4] error_code+116
>> Can be anything. But if I understand anything, this memory is used
>> because someone has requested a page that is swapped out. So the memory
>> must be used, but not reflected in meminfo, and not by a process?
> What you should do is to cause the system to free as many pages as possible
> before looking ad /proc/page_owner. For example, build `usemem' from
> http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz, run
>
> usemem -m N (where N is the number of megabytes which the machine has)
>
> a couple of times. Then check /proc/meminfo, and look to see which pages
> are left over in /proc/page_owner.
Well, I was too lazy to get this utility, used my own to allocate and
fill enough memory as to go some 50MB to deep swap (Did I understand
correctly what usemem does?). Top 3 did not change, except for exact
numbers.
next prev parent reply other threads:[~2006-11-25 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 6:26 2.6.19-rc1-mm1+ memory problem Michael Raskin
2006-11-20 18:18 ` Michael Raskin
2006-11-21 8:37 ` Andrew Morton
[not found] ` <4563485B.3050801@mail.ru>
2006-11-21 19:45 ` Andrew Morton
2006-11-21 21:18 ` Michael Raskin
2006-11-24 13:23 ` Michael Raskin
2006-11-24 23:07 ` Michael Raskin
2006-11-25 19:03 ` Andrew Morton
2006-11-25 21:53 ` Michael Raskin [this message]
2006-11-29 4:29 ` 2.6.19-rc6-mm2 is ok (2.6.19-rc1-mm1+ memory problem) Michael Raskin
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=4568BB4F.2070701@mail.ru \
--to=a1d23ab4@mail.ru \
--cc=akpm@osdl.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.