Re: [PATCH 6.11 000/817] 6.11.11-rc1 review

From: Jon Hunter
Date: Thu Dec 05 2024 - 09:46:18 EST



On 05/12/2024 14:39, Jon Hunter wrote:
On Tue, 03 Dec 2024 15:32:52 +0100, Greg Kroah-Hartman wrote:
-----------
Note, this is will probably be the last 6.11.y kernel to be released.
Please move to the 6.12.y branch at this time.
-----------

This is the start of the stable review cycle for the 6.11.11 release.
There are 817 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 Thu, 05 Dec 2024 14:36:47 +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/v6.x/stable-review/patch-6.11.11-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-6.11.y
and the diffstat can be found below.

thanks,

greg k-h

Failures detected for Tegra ...

Test results for stable-v6.11:
10 builds: 10 pass, 0 fail
26 boots: 26 pass, 0 fail
111 tests: 109 pass, 2 fail

Linux version: 6.11.11-rc1-g57f39ce086c9
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: cpufreq
tegra186-p2771-0000: mmc-dd-urandom.sh


This is a known issue in the mainline that was not caught for Linux v6.12. It is intermittent and so not easily caught. It landed in stable before this cycle and so nothing we can resolve on this cycle. The good news is that a fix [0] has been identified and once in mainline we can backport for stable. It is a networking issue that is causing random test failures when running with NFS.

With that for this update ...

Tested-by: Jon Hunter <jonathanh@xxxxxxxxxx>

Jon

[0] https://lore.kernel.org/netdev/20241205091830.3719609-1-0x1207@xxxxxxxxx/

--
nvpublic