From: "Barry K. Nathan" <barryn@pobox.com>
To: Ron Economos <re@w6rz.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.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@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: freeze during boot regression Re: [PATCH 6.12 000/265] 6.12.77-rc1 review
Date: Fri, 13 Mar 2026 01:05:04 -0700 [thread overview]
Message-ID: <1c54210a-e197-4eb9-88b5-2ed2589c7230@pobox.com> (raw)
In-Reply-To: <2a313336-ccfc-42b7-a14d-c116733ef64a@w6rz.net>
On 3/12/26 23:10, Ron Economos wrote:
> Probably those sched/fair patches.
Yes, after bisecting it turned out to be
sched-fair-fix-eevdf-entity-placement-bug-causing-sc.patch
Taking 6.12.77-rc1 and reverting both of the sched-fair patches
results in a working kernel that boots consistently (which I am
using now to send this email).
--
-Barry K. Nathan <barryn@pobox.com>
next prev parent reply other threads:[~2026-03-13 8:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:06 Greg Kroah-Hartman
2026-03-12 20:41 ` Brett A C Sheffield
2026-03-13 3:25 ` Shuah Khan
2026-03-13 5:32 ` freeze during boot regression " Barry K. Nathan
2026-03-13 5:55 ` Barry K. Nathan
2026-03-13 6:10 ` Ron Economos
2026-03-13 7:27 ` Francesco Dolcini
2026-03-13 8:05 ` Barry K. Nathan [this message]
2026-03-13 9:37 ` Ron Economos
2026-03-13 10:53 ` Barry K. Nathan
2026-03-13 13:38 ` Barry K. Nathan
2026-03-13 13:49 ` Greg Kroah-Hartman
2026-03-13 13:05 ` Mark Brown
2026-03-13 16:16 ` Jon Hunter
2026-03-13 16:18 ` Jon Hunter
2026-03-13 17:02 ` Florian Fainelli
2026-03-13 21:10 ` 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=1c54210a-e197-4eb9-88b5-2ed2589c7230@pobox.com \
--to=barryn@pobox.com \
--cc=achill@achill.org \
--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=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=re@w6rz.net \
--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
Powered by JetHome