From: Michael Ellerman <mpe@ellerman•id.au>
To: Hugh Dickins <hughd@google•com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux•vnet.ibm.com>
Cc: linux-mm@kvack•org, linuxppc-dev@lists•ozlabs.org
Subject: Re: Problems with swapping in v4.5-rc on POWER
Date: Thu, 25 Feb 2016 15:12:30 +1100 [thread overview]
Message-ID: <1456373550.30375.3.camel@ellerman.id.au> (raw)
In-Reply-To: <alpine.LSU.2.11.1602241716220.15121@eggly.anvils>
On Wed, 2016-02-24 at 18:10 -0800, Hugh Dickins via Linuxppc-dev wrote:
> I've plagiarized the subject from Paulus's "Problems with THP" mail
> last weekend; but my similar problems are on PowerMac G5 baremetal,
> with 4kB pages, not capable of THP and no THP configured in.
>
> Under heavily swapping load, running kernel builds on tmpfs in limited
> memory, I've been seeing random segfaults too, internal compiler errors
> etc. Not easily reproduced: sometimes happens in minutes, sometimes
> not for several hours.
>
> I tried and failed to construct a reproducer for you: my lack of a good
> recipe has deterred me from reporting it, and seeing Paulus's mail on
> THP gave me hope that the answer would come up in that thread; but no,
> that was quickly resolved as a THP issue, since fixed.
>
> (Mine had appeared to be fixed in v4.5-rc4 anyway; but I guess I
> just didn't try hard enough, it resurfaced on -rc5 immediately.)
>
> I've seen no sign of such problems on x86. And I saw no sign of such
> problems on v4.4-rc8-mm1, when I included the fixes to the _PAGE_PTE
> and _PAGE_SWP_SOFT_DIRTY swapoff issues we discussed back then (in
> 33 hours of load, should be good enough; but did see such problems
> a couple of times before including those fixes - I took them to be
> a side-effect of the page flags issue, but now rather doubt that).
>
> The minutes or hours thing: I wonder if that indicates a missing
> initialization somewhere: that can easily show up soon after booting,
> but then the machine settles into a steady state of reusing the same
> structures, now initialized; until much later something disturbs the
> state and it has to allocate more. Sheer speculation, but I wonder.
Thanks Hugh.
I do run tests on G5, but obviously not rigorously enough. I kicked off a few
kernel builds on mine and it survived, though once it hits swap it's almost
unusably slow. I'll leave it running overnight and see if I hit anything.
cheers
next prev parent reply other threads:[~2016-02-25 4:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 2:10 Problems with swapping in v4.5-rc on POWER Hugh Dickins
2016-02-25 4:12 ` Michael Ellerman [this message]
2016-02-25 5:36 ` Hugh Dickins
2016-02-25 4:52 ` Aneesh Kumar K.V
2016-02-25 5:43 ` Hugh Dickins
2016-02-25 21:35 ` Hugh Dickins
2016-02-26 10:04 ` Hugh Dickins
2016-03-02 20:49 ` Hugh Dickins
2016-03-03 5:51 ` Michael Ellerman
2016-03-04 17:58 ` Hugh Dickins
2016-03-07 3:00 ` Michael Ellerman
2016-03-08 11:49 ` Hugh Dickins
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=1456373550.30375.3.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=aneesh.kumar@linux$(echo .)vnet.ibm.com \
--cc=hughd@google$(echo .)com \
--cc=linux-mm@kvack$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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