From: Michael Ellerman <mpe@ellerman.id.au>
To: Hugh Dickins <hughd@google.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Paul Mackerras <paulus@ozlabs.org>,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: Problems with swapping in v4.5-rc on POWER
Date: Mon, 07 Mar 2016 14:00:27 +1100 [thread overview]
Message-ID: <1457319627.19197.1.camel@ellerman.id.au> (raw)
In-Reply-To: <alpine.LSU.2.11.1603040948250.5477@eggly.anvils>
On Fri, 2016-03-04 at 09:58 -0800, Hugh Dickins wrote:
>
> The alternative bisection was as unsatisfactory as the first:
> again it fingered an irrelevant merge (rather than any commit
> pulled in by that merge) as the bad commit.
>
> It seems this issue is too intermittent for bisection to be useful,
> on my load anyway.
Darn. Thanks for trying.
> The best I can do now is try v4.4 for a couple of days, to verify that
> still comes out good (rather than the machine going bad coincident with
> v4.5-rc), then try v4.5-rc7 to verify that that still comes out bad.
Thanks, that would still be helpful.
> I'll report back on those; but beyond that, I'll have to leave it to you.
I haven't had any luck here :/
Can you give us a more verbose description of your test setup?
- G5, which exact model?
- 4k pages, no THP.
- how much ram & swap?
- building linus' tree, make -j ?
- source and output on tmpfs? (how big?)
- what device is the swap device? (you said SSD I think?)
- anything else I've forgotten?
Oh and can you send us your bisect logs, we can at least trust the bad results
I think.
cheers
next prev parent reply other threads:[~2016-03-07 3:00 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
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 [this message]
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=1457319627.19197.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@ozlabs.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).