Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 1 Sep 2022 11:50:04 +0200
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Jon Hunter <jonathanh@nvidia.com>
Cc:     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, f.fainelli@gmail.com,
        sudipm.mukherjee@gmail.com, slade@sladewatkins.com,
        "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 5.15 000/136] 5.15.64-rc1 review
Message-ID: <YxCATHEyQapj71yn@kroah.com>
References: <20220829105804.609007228@linuxfoundation.org>
 <e9834880-c16e-e269-30ba-3fa8a94ba1af@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e9834880-c16e-e269-30ba-3fa8a94ba1af@nvidia.com>
Precedence: bulk

On Tue, Aug 30, 2022 at 11:32:24AM +0100, Jon Hunter wrote:
> Hi Greg,
> 
> On 29/08/2022 11:57, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.64 release.
> > There are 136 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, 31 Aug 2022 10:57:37 +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.64-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 have been out on vacation and unfortunately some boot issues were
> introduced for Tegra back in 5.15.61 ...
> 
> Test results for stable-v5.15:
>     10 builds:	10 pass, 0 fail
>     32 boots:	28 pass, 4 fail
>     68 tests:	68 pass, 0 fail
> 
> Linux version:	5.15.64-rc1-g881ab4a7404d
> 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
> 
> Boot failures:	tegra186-p2771-0000, tegra194-p2972-0000,
>                 tegra194-p3509-0000+p3668-0000
> 
> 
> Fortunately, these boot issues are specific to Tegra and were caused by
> commit a7f751d4e830c5a2ac9e9908df43e8d29b7d3b22 ("arm64: tegra: Mark BPMP
> channels as no-memory-wc"). This commit had the fixes tag populated but it
> has a dependency on mainline commit a4740b148a04 ("firmware: tegra: bpmp: Do
> only aligned access to IPC memory area") which did not have any fixes tag
> populated.
> 
> Can you pull mainline commit a4740b148a04 ("firmware: tegra: bpmp: Do only
> aligned access to IPC memory area") into 5.15.y, 5.18.y and 5.19.y? Fine if
> you want to do it for the next stable update.

5.18.y is end-of-life, so I've applied this to the other branches now,
thanks!

greg k-h