linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 30 Apr 2017 15:33:50 +0930	[thread overview]
Message-ID: <99a78105-de58-a5e1-5191-d5f4de7ed5f4@internode.on.net> (raw)
In-Reply-To: <20170427092636.GD4706@dhcp22.suse.cz>



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

I've since restarted that machine, but should it happen again I'd be 
happy to run further tests.

Arthur.

--
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>

  reply	other threads:[~2017-04-30  6:03 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 [this message]
2017-05-02  7:31       ` Michal Hocko
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=99a78105-de58-a5e1-5191-d5f4de7ed5f4@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