From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ian Rogers <irogers@google.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com
Subject: Re: [perf report] 977f739b71: perf-test.skid_test.round2.MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_withou t_NMI_fixed_period.fail
Date: Fri, 2 Oct 2020 16:20:20 +0800 [thread overview]
Message-ID: <ecd17ed2-f041-7a80-b733-7a820e6da9f2@intel.com> (raw)
In-Reply-To: <alpine.LRH.2.20.2009301439250.12057@Diego>
On 9/30/2020 8:41 PM, Michael Petlan wrote:
> Hello. To me, it looks rather a random failure. Is it actually reproducible
> and proven that the patch has caused it? The patch doesn't seem to cause
> the fails below.
Hi Michael,
It's not always reproducible, but we can reproduce it in most cases:
39c0a53b114d0317 977f739b7126bf98b5202e243f6
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:8 75% 6:8
perf-test.skid_test.round2.MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_with_NMI.fail
:8 88% 7:8
perf-test.skid_test.round2.MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_without_NMI_fixed_period.fail
:8 25% 2:8
perf-test.skid_test.round2.MEM_LOAD_RETIRED.L2_HIT_dtlb_with_NMI.fail
:8 62% 5:8
perf-test.skid_test.round2.MEM_LOAD_RETIRED.L2_HIT_dtlb_without_NMI_fixed_period.fail
Best Regards,
Rong Chen
> Cheers,
> Michael
>
> On Wed, 30 Sep 2020, kernel test robot wrote:
>> Greeting,
>>
>> FYI, we noticed the following commit (built with gcc-9):
>>
>> commit: 977f739b7126bf98b5202e243f60cbc0a1ec2c3b ("perf report: Disable ordered_events for raw dump")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>
>>
>> in testcase: perf-test
>> version: perf-test-x86_64-git-1_20200717
>> with following parameters:
>>
>> type: lkp
>> ucode: 0xd6
>>
>> test-description: The internal Perf Test suite.
>>
>>
>> on test machine: 4 threads Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz with 32G memory
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>>
>>
>> If you fix the issue, kindly add following tag
>> Reported-by: kernel test robot <rong.a.chen@intel.com>
>>
>>
>> 2020-09-28 17:02:40 ./skid_test/run.sh
>> Mon Sep 28 17:02:58 UTC 2020
>> 3 test cases pass for skid_test test. 3 test cases fail for skid_test test.
>> Test Case BR_INST_RETIRED.ALL_BRANCHES_PEBS_triad_loop_with_NMI PASS!
>> Test Case MEM_LOAD_RETIRED.L2_HIT_dtlb_with_NMI PASS!
>> Test Case MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_with_NMI FAILED!
>> Test Case BR_INST_RETIRED.ALL_BRANCHES_PEBS_triad_loop_without_NMI_fixed_period PASS!
>> Test Case MEM_LOAD_RETIRED.L2_HIT_dtlb_without_NMI_fixed_period FAILED!
>> Test Case MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_without_NMI_fixed_period FAILED!
>>
>>
>>
>> To reproduce:
>>
>> git clone https://github.com/intel/lkp-tests.git
>> cd lkp-tests
>> bin/lkp install job.yaml # job file is attached in this email
>> bin/lkp run job.yaml
>>
>>
>>
>> Thanks,
>> Rong Chen
>>
>>
>
prev parent reply other threads:[~2020-10-02 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 9:19 [perf report] 977f739b71: perf-test.skid_test.round2.MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_without_NMI_fixed_period.fail kernel test robot
2020-09-30 12:41 ` [perf report] 977f739b71: perf-test.skid_test.round2.MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_withou t_NMI_fixed_period.fail Michael Petlan
2020-10-02 5:42 ` Philip Li
2020-10-02 8:20 ` Chen, Rong A [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=ecd17ed2-f041-7a80-b733-7a820e6da9f2@intel.com \
--to=rong.a.chen@intel.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®