From: Stian Halseth <stian@itx.no>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] Scheduler updates for v7.4
Date: Sat, 31 Oct 2026 09:03:16 +0100 [thread overview]
Message-ID: <1350c2fef9f74d5654041c99d255a22885fa0ec2.camel@itx.no> (raw)
In-Reply-To: <CAHk-=winC2u2D1FAX5grfq9F=bxmARxhuiQ4MvHAiJFu3iF6gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Hi Linus,
On Fri, 2026-10-30 at 14:05 -1000, Linus Torvalds wrote:
> On Sun, 18 Oct 2026 at 00:43, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Please pull the latest sched/core Git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-core-
> > 2026-10-18
>
> So this seems to trigger for me on my laptop. Not every boot, but I've
> seen it at least twice now:
>
> > Stian Halseth (1):
> > sched/cputime: Don't account idle time twice after dyntick-idle
>
> where the new WARN_ON_ONCE() triggers at boot, resulting in a splat like
> this
>
Sorry about that. Paul Menzel and Breno Leitao hit the same.
Nothing is accounted wrong, the warning is just wrong, and the fix Thorsten
linked drops it:
https://lore.kernel.org/all/20261025100202.2584654-1-stian@itx.no/
Since this is getting more attention, I'll send a v2 with a better commit
message and the reports added.
/Stian
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-31 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 10:43 Ingo Molnar
2026-10-20 23:10 ` pr-tracker-bot
2026-10-31 0:05 ` Linus Torvalds
2026-10-31 6:12 ` Thorsten Leemhuis
2026-10-31 8:03 ` Stian Halseth [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=1350c2fef9f74d5654041c99d255a22885fa0ec2.camel@itx.no \
--to=stian@itx.no \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®