From: Ivan Danov <huhavel@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Simon Jeons <simon.jeons@gmail.com>,
linux-mm@kvack.org, 1162073@bugs.launchpad.net
Subject: Re: System freezes when RAM is full (64-bit)
Date: Fri, 05 Apr 2013 12:13:11 +0200 [thread overview]
Message-ID: <515EA3B7.5030308@gmail.com> (raw)
In-Reply-To: <20130404151658.GJ29911@dhcp22.suse.cz>
Tried with vm.swappiness=60, but the only improvement is that now the
mouse input is less choppy than before, but still the problem remains -
the computer is not usable at all, one could not even stop the program,
causing the problem.
Best,
Ivan
--
On 04/04/13 17:16, Michal Hocko wrote:
> On Thu 04-04-13 16:10:06, Ivan Danov wrote:
>> Hi Michal,
>>
>> Yes, I use swap partition (2GB), but I have applied some things for
>> keeping the life of the SSD hard drive longer. All the things I have
>> done are under point 3. at
>> http://www.rileybrandt.com/2012/11/18/linux-ultrabook/.
> OK, I guess I know what's going on here.
> So you did set vm.swappiness=0 which (for some time) means that there is
> almost no swapping going on (although you have plenty of swap as you are
> mentioning above).
> This shouldn't be a big deal normally but you are also backing your
> /tmp on tmpfs which is in-memory filesystem. This means that if you
> are writing to /tmp a lot then this content will fill up your memory
> which is not swapped out until the memory reclaim is getting into real
> troubles - most of the page cache is dropped by that time so your system
> starts trashing.
>
> I would encourage you to set swappiness to a more reasonable value (I
> would use the default value which is 60). I understand that you are
> concerned about your SSD lifetime but your user experience sounds like a
> bigger priority ;)
>
>> By system freezes, I mean that the desktop environment doesn't react
>> on my input. Just sometimes the mouse is reacting very very choppy
>> and slowly, but most of the times it is not reacting at all. In the
>> attached file, I have the output of the script and the content of
>> dmesg for all levels from warn to emerg, as well as my kernel config.
> I haven't checked your attached data but you should get an overview from
> Shmem line from /proc/meminfo which tells you how much shmem/tmpfs
> memory you are using and grep "^Swap" /proc/meminfo will tell you more
> about your swap usage.
>
>> Best,
>> Ivan
> HTH
--
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 prev parent reply other threads:[~2013-04-05 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 19:14 System freezes when RAM is full (64-bit) Ivan Danov
2013-04-03 12:12 ` Michal Hocko
2013-04-04 0:27 ` Simon Jeons
2013-04-04 7:08 ` Michal Hocko
2013-04-04 14:10 ` Ivan Danov
2013-04-04 15:16 ` Michal Hocko
2013-04-05 10:13 ` Ivan Danov [this message]
2013-04-05 11:59 ` Michal Hocko
2013-04-05 20:41 ` Ivan Danov
2013-04-12 10:20 ` Michal Hocko
2013-04-12 10:49 ` Ivan Danov
2013-04-12 11:11 ` Michal Hocko
2013-04-12 12:38 ` Ivan Danov
2013-04-14 14:58 ` Michal Hocko
2013-05-14 15:25 ` Ivan Danov
2013-04-15 5:03 ` Simon Jeons
2013-04-15 14:12 ` Michal Hocko
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=515EA3B7.5030308@gmail.com \
--to=huhavel@gmail.com \
--cc=1162073@bugs.launchpad.net \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=simon.jeons@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 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.