From: Frederic Weisbecker <frederic@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>, Stian Halseth <stian@itx.no>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] Scheduler updates for v7.4
Date: Sat, 31 Oct 2026 14:30:13 +0100 [thread overview]
Message-ID: <auXtZQukFeJy4Ehc@pavilion.home> (raw)
In-Reply-To: <CAHk-=winC2u2D1FAX5grfq9F=bxmARxhuiQ4MvHAiJFu3iF6gw@mail.gmail.com>
Le Fri, Oct 30, 2026 at 02:05:36PM -1000, Linus Torvalds a écrit :
> 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
>
> now < tick_start
> WARNING: kernel/sched/cputime.c:481 at
> kcpustat_dyntick_stop+0x82/0x90, CPU#2: swapper/2/0
> Modules linked in:
> CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted
> 7.3.0-19045-gb92f6e90cf05 #7 PREEMPT(lazy)
> Hardware name: Dell Inc. XPS 13 9380/0KTW76, BIOS 1.26.0 09/11/2023
> RIP: 0010:kcpustat_dyntick_stop+0x82/0x90
> Call Trace:
> <TASK>
> tick_nohz_idle_exit+0xaf/0x140
> do_idle+0x1f5/0x2e0
> cpu_startup_entry+0x20/0x30
> start_secondary+0xf0/0x120
> common_startup_64+0x13e/0x148
> </TASK>
>
> I haven't tried to figure out why, I'm just notifying the guilty parties...
Sorry about that, Stian has a fix, I'm just trying to wrap my head around it before
giving a final ACK.
Thanks.
--
Frederic Weisbecker
SUSE Labs
prev parent reply other threads:[~2026-10-31 13:30 UTC|newest]
Thread overview: 6+ 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
2026-10-31 13:30 ` Frederic Weisbecker [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=auXtZQukFeJy4Ehc@pavilion.home \
--to=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stian@itx.no \
--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®