From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Genes Lists <lists@sapience.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 6.12.2
Date: Fri, 6 Dec 2024 00:07:29 +0100 [thread overview]
Message-ID: <01a7263b-3739-582e-aade-6d9d9495500d@applied-asynchrony.com> (raw)
In-Reply-To: <bad6ec6fc4e8d43198c0873f2e92d324dc1343eb.camel@sapience.com>
On 2024-12-05 23:04, Genes Lists wrote:
> On Thu, 2024-12-05 at 14:53 +0100, Greg Kroah-Hartman wrote:
>> I'm announcing the release of the 6.12.2 kernel.
>>
>
> 6.12.1 works fine but 6.12.2 generates lots of errors during
> boot. Tried on several machines all exhibit the same issue. This one is
> an older lenovo laptop. They do boot and appear to be working but the
> boot errors are worrisome.
>
> It's been several hours since 12.2.2 was released, so others may not
> have a problem?
As Linus has indicated in:
https://lore.kernel.org/stable/CAHk-=whGd0dfaJNiWSR60HH5iwxqhUZPDWgHCQd446gH2Wu0yQ@mail.gmail.com/
the problem is the missing commit b23decf8ac91 ("sched: Initialize idle tasks
only once"). Applying that on top of 6.12.2 fixes the problem.
We just encountered this issue in Gentoo as well when releasing a new kernel
and adding that patch has resolved the issue.
> Thought it best to share before I start to work on bisect. config and
> dmesg outputs attached.
No need to, just add b23decf8ac91 :)
cheers
Holger
next prev parent reply other threads:[~2024-12-05 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 13:53 Greg Kroah-Hartman
2024-12-05 13:53 ` Greg Kroah-Hartman
2024-12-05 22:04 ` Genes Lists
2024-12-05 23:07 ` Holger Hoffstätte [this message]
2024-12-05 23:24 ` Genes Lists
2024-12-06 5: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=01a7263b-3739-582e-aade-6d9d9495500d@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@sapience.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®