All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milos Jakovljevic <sukijaki@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
	Dave Hansen <dave@linux.vnet.ibm.com>
Subject: Re: [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime.
Date: Fri, 16 Nov 2012 00:11:43 +0100	[thread overview]
Message-ID: <1353021103.6409.31.camel@c2d-desktop.mypicture.info> (raw)
In-Reply-To: <20121115141258.8e5cc669.akpm@linux-foundation.org>

On Thu, 2012-11-15 at 14:12 -0800, Andrew Morton wrote: 
> On Thu, 15 Nov 2012 15:05:49 +0100
> Milos Jakovljevic <sukijaki@gmail.com> wrote:
> 
> > Here is the requested content:
> > 
> > free -m: http://pastebin.com/vb878a9Y
> > cat /proc/meminfo : http://pastebin.com/zUDFcYEW
> > cat /proc/slabinfo : http://pastebin.com/kswsJ7Hk
> > cat /proc/vmstat : http://pastebin.com/wUebJqJe
> > 
> > dmesg -c : http://pastebin.com/f7cTu8Wv
> > 
> > echo m > /proc/sysrq-trigger && dmesg : http://pastebin.com/p68DcHUy
> > 
> > And here are also files with that content:
> > http://ubuntuone.com/5GUVahBTiZRP0QjQdP3gkQ
> > 
> 
> You've lost 2-3GB of ZONE_NORMAL and I see no sign there to indicate
> where it went.
> 
> /proc/slabinfo indicates that it isn't a slab leak, and kmemleak won't
> tell us about alloc_pages() leaks.  I'm stumped.  Dave, any progress at
> your end?
> 
> 
I didn't understood anything you sad, but never mind. 

In -rc2 there was a problem with massive iowait when anything was done
(starting an app, loading a web page, etc ...), and there was a massive
read operation from my /home partition. In -rc3 that stopped, and this
started happening. Maybe it is related somehow?

Or maybe, it is just some problem with nvidia blob and 3.7 kernel
loosing VM_RELEASE  (in a blob's mmap.c it was replaced with
VM_DONTEXPAND | VM_DONTDUMP ).  - or maybe I'm just saying nonsense
here.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-11-15 23:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-50181-27@https.bugzilla.kernel.org/>
2012-11-13 22:03 ` [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime Andrew Morton
2012-11-13 23:04   ` Milos Jakovljevic
2012-11-15 14:05   ` Milos Jakovljevic
2012-11-15 22:12     ` Andrew Morton
2012-11-15 23:11       ` Milos Jakovljevic [this message]
2012-11-16 18:34         ` Dave Hansen
2012-11-16 18:46           ` Milos Jakovljevic
2012-11-16 19:15           ` Andrew Morton
2012-11-16 23:59             ` Dave Hansen
2012-11-17 23:08               ` 3.7-rc6 memory accounting problem (manifests like a memory leak) Dave Hansen
2012-11-19 16:44               ` [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime Dave Hansen
2012-11-16  2:51       ` Dave Hansen

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=1353021103.6409.31.camel@c2d-desktop.mypicture.info \
    --to=sukijaki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.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.