All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
	patches@kernelci.org,
	Ben Hutchings <ben.hutchings@codethink.co.uk>,
	lkft-triage@lists.linaro.org,
	linux- stable <stable@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	jolsa@redhat.com, Namhyung Kim <namhyung@kernel.org>,
	Leo Yan <leo.yan@linaro.org>, Basil Eljuse <Basil.Eljuse@arm.com>
Subject: Re: [PATCH 5.7 000/243] 5.7.10-rc2 review
Date: Wed, 22 Jul 2020 14:49:53 +0200	[thread overview]
Message-ID: <20200722124953.GE3155653@kroah.com> (raw)
In-Reply-To: <CA+G9fYuVJAHyXqPhhqtcdDstKrjb-TLu=d7DZTuQX3YuCsypHA@mail.gmail.com>

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@linuxfoundation.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

  reply	other threads:[~2020-07-22 12:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 19:16 [PATCH 5.7 000/243] 5.7.10-rc2 review Greg Kroah-Hartman
2020-07-20 23:37 ` Shuah Khan
2020-07-21 10:42   ` Greg Kroah-Hartman
2020-07-21  9:29 ` Naresh Kamboju
2020-07-22 12:49   ` Greg Kroah-Hartman [this message]
2020-07-23 15:09     ` Naresh Kamboju
     [not found] ` <20200720191523.845282610-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
2020-07-21 13:17   ` Thierry Reding
2020-07-21 13:17     ` Thierry Reding
2020-07-22 12:47     ` Greg Kroah-Hartman
2020-07-21 16:38 ` Guenter Roeck
2020-07-22 12:49   ` Greg Kroah-Hartman

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=20200722124953.GE3155653@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Basil.Eljuse@arm.com \
    --cc=acme@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.