From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Michal Hocko <mhocko@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 4.11.0-rc8+/x86_64 desktop lockup until applications closed
Date: Wed, 3 May 2017 11:11:01 +0930 [thread overview]
Message-ID: <73bb8828-e586-0aee-506b-5a7b6f87384a@internode.on.net> (raw)
In-Reply-To: <20170502073138.GA14593@dhcp22.suse.cz>
Michal Hocko wrote on 02/05/17 17:01:
>> [92311.944443] swap_info_get: Bad swap offset entry 000ffffd
>> [92311.944449] swap_info_get: Bad swap offset entry 000ffffe
>> [92311.944451] swap_info_get: Bad swap offset entry 000fffff
>
> Pte swap entry seem to be clobbered. That suggests a deeper problem and
> a memory corruption.
Thanks again for the feedback. I've gone with 4.11.0+ git head kernels
and last night rather than a lock-up I saw:
[40050.937161] mmap: chromium (6060): VmData 2148573184 exceed data
ulimit 2147483647. Update limits or use boot option ignore_rlimit_data.
[40051.183213] traps: chromium[6060] trap int3 ip:5642ccce7996
sp:7ffe0a563ac0 error:0
and the desktop session remained responsive.
The 2 GiB ulimit is preferable for me than having to rely on the OOM
killer, but I can run tests with ignore_rlimit_data later on to check
that the OOM killer still works rather than hitting some unforeseen
error on swap exhaustion.
Arthur.
prev parent reply other threads:[~2017-05-03 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <md5:RQiZYAYNN/yJzTrY48XZ7w==>
2017-04-27 9:06 ` 4.11.0-rc8+/x86_64 desktop lockup until applications closed Arthur Marsh
2017-04-27 9:26 ` Michal Hocko
2017-04-30 6:03 ` Arthur Marsh
2017-05-02 7:31 ` Michal Hocko
2017-05-03 1:41 ` Arthur Marsh [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=73bb8828-e586-0aee-506b-5a7b6f87384a@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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 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).