From: "AL13N" <alien@rmail.be>
To: linux-kernel@vger.kernel.org
Cc: "Pavel Machek" <pavel@ucw.cz>
Subject: Re: Memory leaks on atom-based boards?
Date: Fri, 21 Nov 2014 21:08:37 -0000 [thread overview]
Message-ID: <2922e9932862ff847052dabae293c4e0.squirrel@mail.rmail.be> (raw)
In-Reply-To: <20141121200622.GB26833@amd>
err
the whole point is that swap stays largely unused and get OOM after 3 or 4
days on only atom boards (2), while the other machines(5) with the
identical kernel are unaffected by this and can run for several months...
plus, upgrade to 3.17.2 seems to have fixed the issue...
it's categorized as a slow and steady decline in MemAvailable in
/proc/meminfo.
i can report that the server in question is now running since i fixed it,
several weeks now, and MemAvailable is still above 3GB ...
prev parent reply other threads:[~2014-11-21 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 18:44 Memory leaks on atom-based boards? AL13N
2014-11-09 11:56 ` Vlastimil Babka
2014-11-09 16:38 ` AL13N
2014-11-09 22:07 ` Vlastimil Babka
2014-11-10 0:19 ` AL13N
2014-11-21 20:06 ` Pavel Machek
2014-11-21 21:08 ` AL13N [this message]
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=2922e9932862ff847052dabae293c4e0.squirrel@mail.rmail.be \
--to=alien@rmail.be \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).