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.12 000/590] 6.12.13-rc1 review
Date: Thu, 6 Feb 2025 12:04:14 +0000 [thread overview]
Message-ID: <8ab5ab07-fb63-4235-bdb1-f4acbe86f8bc@nvidia.com> (raw)
In-Reply-To: <b7363e74-2207-4cab-a573-bc552b901f4e@nvidia.com>
On 06/02/2025 11:41, Jon Hunter wrote:
> Hi Greg,
>
> On 06/02/2025 11:37, Jon Hunter wrote:
>> On Wed, 05 Feb 2025 14:35:55 +0100, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 6.12.13 release.
>>> There are 590 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 Fri, 07 Feb 2025 13:43:01 +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.12.13-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.12.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> Failures detected for Tegra ...
>>
>> Test results for stable-v6.12:
>> 10 builds: 10 pass, 0 fail
>> 26 boots: 26 pass, 0 fail
>> 116 tests: 115 pass, 1 fail
>>
>> Linux version: 6.12.13-rc1-g9ca4cdc5e984
>> 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: tegra194-p2972-0000: pm-system-suspend.sh
>
>
> I am seeing a suspend regression on both 6.12.y and 6.13.y and bisect is
> pointing to the following commit ...
>
> # first bad commit: [ca20473b60926b94fdf58f971ccda43e866c32d1] PM:
> sleep: core: Synchronize runtime PM status of parents and children
And 6.6.y too!
Jon
--
nvpublic
next prev parent reply other threads:[~2025-02-06 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250205134455.220373560@linuxfoundation.org>
2025-02-06 11:37 ` [PATCH 6.12 000/590] 6.12.13-rc1 review Jon Hunter
2025-02-06 11:41 ` Jon Hunter
2025-02-06 12:04 ` Jon Hunter [this message]
2025-02-06 14:47 ` Greg Kroah-Hartman
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=8ab5ab07-fb63-4235-bdb1-f4acbe86f8bc@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