From: Andrew Morton <akpm@linux-foundation.org>
To: sukijaki@gmail.com
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: Re: [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime.
Date: Tue, 13 Nov 2012 14:03:52 -0800 [thread overview]
Message-ID: <20121113140352.4d2db9e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-50181-27@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 6 Nov 2012 15:11:48 +0000 (UTC)
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=50181
>
> Summary: Memory usage doubles after more then 20 hours of
> uptime.
> Product: Memory Management
> Version: 2.5
> Kernel Version: 3.7-rc3 and 3.7-rc4
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: akpm@linux-foundation.org
> ReportedBy: sukijaki@gmail.com
> Regression: Yes
>
>
> Created an attachment (id=85721)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=85721)
> kernel config file
>
> After 20 hours of uptime, memory usage starts going up. Normal usage for my
> system was around 2.5GB max with all my apps and services up and running. But
> with 3.7-rc3 and now -rc4 kernel, after more then 20 hours of uptime, it starts
> to going up. With kernel before 3.7-rc3, my machine could be up for 10 days and
> not go beyond 2.6GB memory usage.
>
> If I start some app that uses a lot of memory, when there is already 4 or even
> 6GB used already, insted of freeing the memory, it starts to swap it, and
> everything slows down with a lot of iowait.
>
> Here is "free -m" output after 24 hours of uptime:
>
> free -m
> total used free shared buffers cached
> Mem: 7989 7563 426 0 146 2772
> -/+ buffers/cache: 4643 3345
> Swap: 1953 688 1264
>
>
> I know that it is ok for memory to be used this much for buffers and cache, but
> it is not normal not to relase it when it is needed.
>
> In attachment is my kernel config file.
>
Sounds like a memory leak.
Please get the machine into this state and then send us
- the contents of /proc/meminfo
- the contents of /proc/slabinfo
- the contents of /proc/vmstat
- as root:
dmesg -c
echo m > /proc/sysrq-trigger
dmesg
thanks.
--
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>
next parent reply other threads:[~2012-11-13 22:03 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 ` Andrew Morton [this message]
2012-11-13 23:04 ` [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime Milos Jakovljevic
2012-11-15 14:05 ` Milos Jakovljevic
2012-11-15 22:12 ` Andrew Morton
2012-11-15 23:11 ` Milos Jakovljevic
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=20121113140352.4d2db9e8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sukijaki@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).