From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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,
hargar@microsoft.com, broonie@kernel.org,
linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.11 000/817] 6.11.11-rc1 review
Date: Thu, 5 Dec 2024 14:45:55 +0000 [thread overview]
Message-ID: <97b972f5-e368-473e-81c0-d241e9ceaa92@nvidia.com> (raw)
In-Reply-To: <525de045-eab9-4346-b4b2-b2111eac38ff@drhqmail201.nvidia.com>
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@nvidia.com>
Jon
[0]
https://lore.kernel.org/netdev/20241205091830.3719609-1-0x1207@gmail.com/
--
nvpublic
prev parent reply other threads:[~2024-12-05 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 14:32 [PATCH 6.11 000/817] 6.11.11-rc1 review Greg Kroah-Hartman
2024-12-03 14:41 ` [PATCH 6.11 527/817] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-03 22:07 ` [PATCH 6.11 000/817] 6.11.11-rc1 review Mark Brown
2024-12-03 22:09 ` Peter Schneider
2024-12-03 22:33 ` Florian Fainelli
2024-12-04 0:23 ` SeongJae Park
2024-12-04 7:16 ` Ron Economos
2024-12-04 13:25 ` Naresh Kamboju
2024-12-04 16:55 ` Shuah Khan
2024-12-04 18:51 ` Miguel Ojeda
2024-12-05 11:05 ` Muhammad Usama Anjum
2024-12-05 14:39 ` Jon Hunter
2024-12-05 14:45 ` Jon Hunter [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=97b972f5-e368-473e-81c0-d241e9ceaa92@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.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