Re: [GIT PULL] Scheduler updates for v7.4

[Thorsten Leemhuis]

On 10/31/26 01:05, Linus Torvalds wrote:
> On Sun, 18 Oct 2026 at 00:43, Ingo Molnar <mingo@xxxxxxxxxx> 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

Not my area of expertise, as usual, but FWIW: a fix for that one that
from a brief look is about the issue you are seeing is discussed here:

sched/cputime: Don't warn when the tick period starts after idle exit
https://lore.kernel.org/all/20261025100202.2584654-1-stian@xxxxxx/

Ciao, Thorsten
> 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...
> 
>                 Linus