public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Genes Lists <lists@sapience.com>
Cc: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 6.12.2
Date: Fri, 6 Dec 2024 06:47:45 +0100	[thread overview]
Message-ID: <2024120628-repressed-unveiled-1085@gregkh> (raw)
In-Reply-To: <136fbb7aedc6e3750f8361309609ddf4283cd91d.camel@sapience.com>

On Thu, Dec 05, 2024 at 06:24:36PM -0500, Genes Lists wrote:
> On Fri, 2024-12-06 at 00:07 +0100, Holger Hoffstätte wrote:
> > > 6.12.1 works fine but 6.12.2 generates lots of errors during
> ...
> > 
> > 
> > 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....
> 
> > No need to, just add b23decf8ac91 :)
> > 
> > cheers
> > Holger
> > 
> Excellent - missed that completely. 
> I will stop bisecting now, thank you so much.

Sorry about this, I'll go push out a new kernel with this fix in it now.

greg k-h

      reply	other threads:[~2024-12-06  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 13:53 Linux 6.12.2 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
2024-12-05 23:24     ` Genes Lists
2024-12-06  5:47       ` Greg Kroah-Hartman [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=2024120628-repressed-unveiled-1085@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=holger@applied-asynchrony.com \
    --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