From: Qian Cai <cai@lca.pw>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: LTP hugemmap05 test case failure on arm64 with linux-next (next-20190613)
Date: Sun, 16 Jun 2019 21:41:09 -0400 [thread overview]
Message-ID: <EC704BC3-62FF-4DCE-8127-40279ED50D65@lca.pw> (raw)
In-Reply-To: <054b6532-a867-ec7c-0a72-6a58d4b2723e@arm.com>
> On Jun 16, 2019, at 9:32 PM, Anshuman Khandual <anshuman.khandual@arm.com> wrote:
>
> Hello Qian,
>
> On 06/14/2019 05:45 PM, Qian Cai wrote:
>> On Fri, 2019-06-14 at 11:20 +0100, Will Deacon wrote:
>>> Hi Qian,
>>>
>>> On Thu, Jun 13, 2019 at 05:34:01PM -0400, Qian Cai wrote:
>>>> LTP hugemmap05 test case [1] could not exit itself properly and then degrade
>>>> the
>>>> system performance on arm64 with linux-next (next-20190613). The bisection
>>>> so
>>>> far indicates,
>>>>
>>>> BAD: 30bafbc357f1 Merge remote-tracking branch 'arm64/for-next/core'
>>>> GOOD: 0c3d124a3043 Merge remote-tracking branch 'arm64-fixes/for-next/fixes'
>>>
>>> Did you finish the bisection in the end? Also, what config are you using
>>> (you usually have something fairly esoteric ;)?
>>
>> No, it is still running.
>>
>> https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
>>
>
> Were you able to bisect the problem till a particular commit ?
Not yet, it turned out the test case needs to run a few times (usually within 5) to reproduce, so the previous bisection was totally wrong where it assume the bad commit will fail every time. Once reproduced, the test case becomes unkillable stuck in the D state.
I am still in the middle of running a new round of bisection. The current progress is,
35c99ffa20ed GOOD (survived 20 times)
def0fdae813d BAD
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-17 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 21:34 LTP hugemmap05 test case failure on arm64 with linux-next (next-20190613) Qian Cai
2019-06-14 10:20 ` Will Deacon
2019-06-14 12:15 ` Qian Cai
2019-06-17 1:32 ` Anshuman Khandual
2019-06-17 1:41 ` Qian Cai [this message]
2019-06-24 9:35 ` Will Deacon
2019-06-24 12:58 ` Qian Cai
2019-06-24 21:30 ` Qian Cai
2019-06-24 21:53 ` Mike Kravetz
2019-06-27 18:09 ` Mike Kravetz
2019-06-27 18:54 ` Qian Cai
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=EC704BC3-62FF-4DCE-8127-40279ED50D65@lca.pw \
--to=cai@lca.pw \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@arm.com \
/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).