From: Michal Hocko <mhocko@kernel.org>
To: Arthur Marsh <arthur.marsh@internode.on.net>
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: Tue, 2 May 2017 09:31:39 +0200 [thread overview]
Message-ID: <20170502073138.GA14593@dhcp22.suse.cz> (raw)
In-Reply-To: <99a78105-de58-a5e1-5191-d5f4de7ed5f4@internode.on.net>
On Sun 30-04-17 15:33:50, Arthur Marsh wrote:
>
>
> Michal Hocko wrote on 27/04/17 18:56:
> >On Thu 27-04-17 18:36:38, Arthur Marsh wrote:
> >[...]
> >>[55363.482931] QXcbEventReader: page allocation stalls for 10048ms, order:0,
> >>mode:0x14200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null)
> >
> >Are there more of these stalls?
>
> I haven't seen the same kinds of logging in dmesg, but a few minutes ago I
> did see that the desktop had locked up and after remotely logging in and
> doing a kill -HUP of iceweasel/firefox, saw this:
>
> [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.
--
Michal Hocko
SUSE Labs
--
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:[~2017-05-02 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <md5:RQiZYAYNN/yJzTrY48XZ7w==>
2017-04-27 9:06 ` Arthur Marsh
2017-04-27 9:26 ` Michal Hocko
2017-04-30 6:03 ` Arthur Marsh
2017-05-02 7:31 ` Michal Hocko [this message]
2017-05-03 1:41 ` Arthur Marsh
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=20170502073138.GA14593@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=arthur.marsh@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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