public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@dsv.su.se>
To: Tobias Hennerich <Tobias@Hennerich.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Strange memory leak in 2.6.x
Date: Fri, 11 Mar 2005 19:23:40 +0100	[thread overview]
Message-ID: <1110565420.2501.12.camel@boxen> (raw)
In-Reply-To: <20050311183207.A22397@bart.hennerich.de>

> > > Please grab 2.6.11, apply the below patch, set CONFIG_PAGE_OWNER and follow
> > > the below instructions.
> > 
> > thank you for you mails. We installed the patch from Alex on a test-system
> > last night and will switch it to the production machine this evening. The
> > problem will start after 48-72 hours, so we hope to send feedback
> > on friday.
> 
> Ok, we had another crash this morning after an uptime of only 36
> hours 8-(.
> 
> No oom-killer this time, but we got a very high load (>40) in the
> end. Our cron-job which starts the page_owner-sort every 10 minutes
> didn't return the last 4 times.
> 
> The new 2.6.11-kernel changed the graphs a little bit - values for
> 'MemTree' are much higher, but values for 'Cached' and 'Buffered' are
> still very low.
> 
> Here the graph for the last week:
> 
>   http://download.hennerich.de/memory-leak2.png
> 
> (the left part is the same like our first graph last week
> http://download.hennerich.de/memory-leak.png, the weekend is well visible)
> 
> Detailed view of the last 40 hours:
> 
>   http://download.hennerich.de/memory-leak3.png
> 
> Some output of the page_owner-sort:
> 
>
>   http://download.hennerich.de/page_owner_sorted_20050311_0820.bz2

Yikes something isn't right with these backtraces that page_owner is
showing. Even without frame pointers it shouldn't be this noisy.

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"

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).

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.

Thanks
Alexander


  reply	other threads:[~2005-03-11 18:49 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 [this message]
2005-03-12 12:32         ` Tobias Hennerich
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=1110565420.2501.12.camel@boxen \
    --to=alexn@dsv.su.se \
    --cc=Tobias@Hennerich.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox