From: Chris Murphy <lists@colorremedies.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Chris Murphy <lists@colorremedies.com>, linux-mm@kvack.org
Subject: Re: user space unresponsive, followup: lsf/mm congestion
Date: Sat, 11 Jan 2020 17:07:17 -0700 [thread overview]
Message-ID: <CAJCQCtRytcxdjEZnGDRRuABC+dWJS0BUr0bzCenVsnc4DXvk5Q@mail.gmail.com> (raw)
In-Reply-To: <20200110110739.GD29802@dhcp22.suse.cz>
On Fri, Jan 10, 2020 at 4:07 AM Michal Hocko <mhocko@kernel.org> wrote:
>
> So you have redirected the output (stdout) to a file. This is less
> effective than using a file directly because the progy makes sure to
> preallocate and mlock the output file data as well. Anyway, let's have a
> look what you managed to gather
[chris@fmac tmp]$ /home/chris/read_vmstat readvmstatwkgtk.out
file:readvmstatwkgtk.out timeout:1.0s buffer_size:10485760
mlockall. Continuing anyway: Cannot allocate memory
Estimated 3744 entries fit to the buffer
^C
This is with vm.swappiness=100, is also ~12 minutes. Responsiveness
appears unchanged. File is attached here:
https://bugzilla.kernel.org/show_bug.cgi?id=206117#c8
More curious is I get a call trace I haven't seen before when I try to
login to this hung system, via ssh. That's in
https://bugzilla.kernel.org/show_bug.cgi?id=206117#c7
--
Chris Murphy
prev parent reply other threads:[~2020-01-12 0:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 20:29 Chris Murphy
2020-01-07 20:58 ` Michal Hocko
2020-01-07 21:25 ` Chris Murphy
2020-01-08 9:25 ` Michal Hocko
2020-01-08 21:14 ` Chris Murphy
2020-01-08 21:18 ` Chris Murphy
2020-01-09 11:51 ` Michal Hocko
2020-01-09 11:53 ` Michal Hocko
2020-01-10 6:12 ` Chris Murphy
2020-01-10 11:07 ` Michal Hocko
2020-01-10 22:27 ` Chris Murphy
2020-01-14 9:46 ` Michal Hocko
2020-01-12 0:07 ` Chris Murphy [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=CAJCQCtRytcxdjEZnGDRRuABC+dWJS0BUr0bzCenVsnc4DXvk5Q@mail.gmail.com \
--to=lists@colorremedies.com \
--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