On Tue, 2012-11-13 at 14:03 -0800, Andrew Morton wrote: > (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@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx > > ReportedBy: sukijaki@xxxxxxxxx > > 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. Will do. But it will take a day or two to get there, I rebooted today because of this problem. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>