[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200722124953.GE3155653@kroah.com>
Date: Wed, 22 Jul 2020 14:49:53 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>,
Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
lkft-triage@...ts.linaro.org,
linux- stable <stable@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
jolsa@...hat.com, Namhyung Kim <namhyung@...nel.org>,
Leo Yan <leo.yan@...aro.org>,
Basil Eljuse <Basil.Eljuse@....com>
Subject: Re: [PATCH 5.7 000/243] 5.7.10-rc2 review
On Tue, Jul 21, 2020 at 02:59:22PM +0530, Naresh Kamboju wrote:
> On Tue, 21 Jul 2020 at 00:46, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.7.10 release.
> > There are 243 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed, 22 Jul 2020 19:14:36 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.10-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Results from Linaro’s test farm.
> Regressions detected on arm and arm64 (Juno-r2)
> We are bisecting this problem and get back to you soon.
>
> perf test cases failed
> perf:
> * Track-with-sched_switch
> * perf_record_test
> * perf_report_test
>
> Bad case:
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.002 MB perf-lava-test.data ]
>
> when it was pass it prints number of samples like below,
> Good case:
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.004 MB perf-lava-test.data (46 samples) ]
>
> steps to reproduce:
> # perf record -e cycles -o perf-lava-test.data ls -a 2>&1 | tee perf-record.log
>
> Link to full test:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-5.7-oe/build/v5.7.9-244-g7d2e5723ce4a/testrun/2969482/suite/perf/test/perf_record_test/log
>
> test case:
> https://github.com/Linaro/test-definitions/blob/master/automated/linux/perf/perf.sh
Any hint by bisection as to what this problem is caused by?
thanks,
greg k-h
Powered by blists - more mailing lists