Re: [BUG] sched: BUG() in select_fallback_rq() at boot with isolcpus=domain on the boot CPU and CONFIG_CPUSETS=n
From: Frederic Weisbecker
Date: Thu Nov 19 2026 - 11:04:07 EST
Le Wed, Nov 18, 2026 at 10:55:35AM -0500, Waiman Long a écrit :
> On 11/18/26 9:49 AM, Frederic Weisbecker wrote:
> > Le Tue, Nov 17, 2026 at 10:13:02AM -0500, Waiman Long a écrit :
> > > On 11/17/26 9:48 AM, Mathieu Desnoyers wrote:
> > > > Hi,
> > > >
> > > > With CONFIG_CPUSETS=n, a kernel booted with isolcpus=domain,0 hits the
> > > > BUG() in select_fallback_rq() during boot. CPU 0 is the boot CPU. I
> > > > found it while testing a SCHED_DEADLINE series [1]. I then reproduced
> > > > it on v7.4-rc2 alone. tip/master of 2026-11-17 and next-20261116 have
> > > > the same code. A proposed fix follows the scissors line.
> > > >
> > > > Trigger
> > > > =======
> > > >
> > > > Build x86-64 with CONFIG_CPUSETS=n. Boot a VM of 4 CPUs with
> > > > isolcpus=domain,0 or isolcpus=domain,0,1. The kernel panics before
> > > > init runs, in every boot.
> > > >
> > > > These boot fine:
> > > > - the same kernel with isolcpus=domain,1,2, or without isolcpus;
> > > > - a kernel with CONFIG_CPUSETS=y, with isolcpus=domain,0,1.
> > > I am now thinking about disallowing the boot CPU from being domain isolated.
> > > That will include using isolcpus=domain boot time isolation parameter as
> > > well as in setting up isolated cpuset partition. Will that be a simpler
> > > solution than fixing all these places where isolating the boot CPU will
> > > cause various problems that need to be fixed?
> > You can try that, hopefully nobody relies on that. nohz_full supports the
> > boot CPU to be isolated but it's a heresy.
>
> The upcoming runtime modification of nohz_full CPU will not support the boot
> CPU
Agreed.
> at least for x86, as the boot CPU cannot be made offline.
We should forbid that on all archs.
> I would not
> recommend putting the boot CPU into nohz_full boot parameter, though we are
> not going to forbid it.
It's already supported and unfortunately we can't remove that as that would
break kernel ABI.
--
Frederic Weisbecker
SUSE Labs