From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@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, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
allen.lkml@gmail.com, broonie@kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 5.15 000/690] 5.15.154-rc1 review
Date: Tue, 9 Apr 2024 14:23:17 +0200 [thread overview]
Message-ID: <2024040953-eclipse-recount-dda9@gregkh> (raw)
In-Reply-To: <04151fac-3bf6-4199-a822-2fbaaef8b77b@nvidia.com>
On Tue, Apr 09, 2024 at 07:53:14AM +0100, Jon Hunter wrote:
> Hi Greg,
>
> On 08/04/2024 13:47, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.154 release.
> > There are 690 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, 10 Apr 2024 12:52:23 +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.15.154-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.15.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
>
> I am seeing a suspend regression on Tegra186 and Tegra194 ...
>
> Test results for stable-v5.15:
> 10 builds: 10 pass, 0 fail
> 26 boots: 26 pass, 0 fail
> 102 tests: 100 pass, 2 fail
>
> Linux version: 5.15.154-rc1-gbfeab055fa43
> Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
> tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
> tegra20-ventana, tegra210-p2371-2180,
> tegra210-p3450-0000, tegra30-cardhu-a04
>
> Test failures: tegra186-p2771-0000: pm-system-suspend.sh
> tegra194-p2972-0000: pm-system-suspend.sh
>
>
> Bisect is pointing to the following commit and reverting this fixes it ...
>
> > NeilBrown <neilb@suse.de>
> > nfsd: don't allow nfsd threads to be signalled.
>
>
> When suspend fails, I see the following error message ...
>
> Freezing of tasks failed after 20.006 seconds (1 tasks refusing to
> freeze, wq_busy=0):
Odd. I'll go drop this commit now, thanks for testing and bisecting!
greg k-h
prev parent reply other threads:[~2024-04-09 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240408125359.506372836@linuxfoundation.org>
2024-04-09 6:53 ` [PATCH 5.15 000/690] 5.15.154-rc1 review Jon Hunter
2024-04-09 12:23 ` Greg Kroah-Hartman [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=2024040953-eclipse-recount-dda9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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 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).