From: Sasha Levin <sashal@kernel.org>
To: Brett A C Sheffield <bacs@librecast.net>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
gregkh@linuxfoundation.org, patches@lists.linux.dev,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@nabladev.com,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.6 000/684] 6.6.128-rc2 review
Date: Wed, 4 Mar 2026 07:14:58 -0500 [thread overview]
Message-ID: <aagiQjT1eBGEHV--@laps> (raw)
In-Reply-To: <aafiF3Mtc17i7Y72@auntie>
On Wed, Mar 04, 2026 at 07:41:11AM +0000, Brett A C Sheffield wrote:
>On 2026-03-02 19:35, Brett A C Sheffield wrote:
>> # Librecast Test Results (FAIL)
>>
>> 020/020 [ OK ] liblcrq
>> 010/010 [ OK ] libmld
>> 120/120 [ OK ] liblibrecast
>>
>> CPU/kernel: Linux auntie 6.6.128-rc2-ge6906aa7f5ea #1 SMP PREEMPT_DYNAMIC Mon Mar 2 17:31:27 -00 2026 x86_64 AMD Ryzen 9 9950X 16-Core Processor AuthenticAMD GNU/Linux
>>
>> Builds, boots and passes network tests. Fails to poweroff.
>>
>> Bisects to commit 3ba77c48498f0fa29456e2435d7d49eafc0a279c (upstream 4589712e0111352973131bad975023b25569287c) and affects 6.6.y and 6.12.y. Other kernels are unaffected, including mainline.
>
>Are we dropping the offending commit from 6.6.y and 6.12.y and retesting?
Yup, I'm going to drop it from both trees.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-04 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:09 [PATCH 6.6 000/684] 6.6.128-rc2 review Sasha Levin
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-04 7:41 ` Brett A C Sheffield
2026-03-04 12:14 ` Sasha Levin [this message]
2026-03-04 13:29 ` Brett A C Sheffield
2026-03-02 21:58 ` Peter Schneider
2026-03-03 5:01 ` Florian Fainelli
2026-03-03 7:36 ` Francesco Dolcini
2026-03-03 8:22 ` Shung-Hsi Yu
2026-03-03 12:20 ` Ron Economos
2026-03-03 19:19 ` Mark Brown
2026-03-03 19:33 ` Shuah Khan
2026-03-03 21:21 ` Miguel Ojeda
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=aagiQjT1eBGEHV--@laps \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=bacs@librecast.net \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@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@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--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