Re: [PATCH 5.17 00/39] 5.17.1-rc1 review

From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Rob Clark <robdclark@chromium.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@denx.de,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, slade@sladewatkins.com
Subject: Re: [PATCH 5.17 00/39] 5.17.1-rc1 review
Date: Sat, 26 Mar 2022 17:56:32 +0530	[thread overview]
Message-ID: <CA+G9fYuPJyH4V1tJEt5P8FrF5w-NF470ZKOBM01nDeHczATqDA@mail.gmail.com> (raw)
In-Reply-To: <Yj7jI6uEtZDC5mQS@kroah.com>

On Sat, 26 Mar 2022 at 15:25, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Sat, Mar 26, 2022 at 10:24:39AM +0530, Naresh Kamboju wrote:
> > On Fri, 25 Mar 2022 at 20:50, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 5.17.1 release.
> > > There are 39 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 Sun, 27 Mar 2022 15:04:08 +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.17.1-rc1.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.17.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > arm64 qcom db410c device crashed [1]
> >
> > [   10.823905] Internal error: Oops: 96000004 [#1] PREEMPT SMP
> > [   10.876029] CPU: 1 PID: 193 Comm: kworker/1:2 Not tainted 5.17.1-rc1 #1
> > [   10.876047] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
> > [   10.876054] Workqueue: pm pm_runtime_work
> > [   10.876076] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> > [   10.876087] pc : hrtimer_active+0x14/0x80
> > [   10.876102] lr : hrtimer_cancel+0x28/0x70
> >
> >
> > The following patch fixes the problem.
> >
> > >From 05afd57f4d34602a652fdaf58e0a2756b3c20fd4 Mon Sep 17 00:00:00 2001
> > From: Rob Clark <robdclark@chromium.org>
> > Date: Tue, 8 Mar 2022 10:48:44 -0800
> > Subject: drm/msm/gpu: Fix crash on devices without devfreq support (v2)
> >
> > Avoid going down devfreq paths on devices where devfreq is not
> > initialized.
> >
> > v2: Change has_devfreq() logic [Dmitry]
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > Reported-by: Anders Roxell <anders.roxell@linaro.org>
> > Signed-off-by: Rob Clark <robdclark@chromium.org>
> > Fixes: 6aa89ae1fb04 ("drm/msm/gpu: Cancel idle/boost work on suspend")
> > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > Link: https://lore.kernel.org/r/20220308184844.1121029-1-robdclark@gmail.com
> > ---
> >  drivers/gpu/drm/msm/msm_gpu_devfreq.c | 30 +++++++++++++++++++++++++-----
> >  1 file changed, 25 insertions(+), 5 deletions(-)
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
>
> Now queued up, but note, this problem was already present in 5.17.0,
> right?

Yeah.
This problem was there and then later it got fixed.

- Naresh