From: Tobias Hennerich <Tobias@Hennerich.de>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Strange memory leak in 2.6.x
Date: Sat, 12 Mar 2005 13:32:41 +0100 [thread overview]
Message-ID: <20050312133241.A11469@bart.hennerich.de> (raw)
In-Reply-To: <1110565420.2501.12.camel@boxen>; from alexn@dsv.su.se on Fri, Mar 11, 2005 at 07:23:40PM +0100
Hello,
On Fri, Mar 11, 2005 at 07:23:40PM +0100, Alexander Nyberg wrote:
> Yikes something isn't right with these backtraces that page_owner is
> showing. Even without frame pointers it shouldn't be this noisy.
If you could send me some pointers to documents how to interpret
this output, i would appreciate it.
> I'm afraid I'm going to need to ask for more help, could you please
> select CONFIG_FRAME_POINTER under
> Kernel hacking => "Compile the kernel with frame pointers"
Done. Our .config looks now like this:
...
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
CONFIG_PAGE_OWNER=y
CONFIG_FRAME_POINTER=y
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
...
> And when that kernel is booted, could you directly send me the output
> of /proc/page_owner (sort or unsorted) so that I can see if something is
> wrong with the data it's producing (just to be sure).
See http://download.hennerich.de/page_owner_sorted_20050312_1040.bz2
> If it works better with CONFIG_FRAME_POINTER, i'm also going to have to
> ask you to do another one of these runs that you just did.
The cronjob which generates each 10 minutes a new actual file of
page_owner_sorted is still running... and I'm afraid that we will
run into problems sooner or later again...
Best regards Tobias
--
T+T Hennerich GmbH --- Zettachring 12a --- 70567 Stuttgart
Fon:+49(711)720714-0 Fax:+49(711)720714-44 Vanity:+49(700)HENNERICH
UNIX - Linux - Java - C Entwicklung/Beratung/Betreuung/Schulung
http://www.hennerich.de/
next prev parent reply other threads:[~2005-03-12 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 12:37 Strange memory leak in 2.6.x Tobias Hennerich
[not found] ` <1110291647.2294.12.camel@boxen>
[not found] ` <20050308154042.A388@bart.hennerich.de>
2005-03-08 16:03 ` Alexander Nyberg
2005-03-09 1:38 ` Andrew Morton
2005-03-09 9:27 ` Tobias Hennerich
2005-03-11 17:32 ` Tobias Hennerich
2005-03-11 18:23 ` Alexander Nyberg
2005-03-12 12:32 ` Tobias Hennerich [this message]
2005-03-12 15:08 ` Alexander Nyberg
2005-03-12 18:08 ` Alexander Nyberg
2005-03-12 20:42 ` Tobias Hennerich
[not found] ` <1110661479.3360.11.camel@boxen>
2005-03-14 12:27 ` Timo Hennerich
2005-03-14 14:58 ` Alexander Nyberg
2005-03-17 12:30 ` Tobias Hennerich
2005-03-23 13:41 ` Alexander Nyberg
2005-03-23 16:57 ` Tobias Hennerich
2005-03-24 15:18 ` Alexander Nyberg
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=20050312133241.A11469@bart.hennerich.de \
--to=tobias@hennerich.de \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--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