Re: [BUG] sched: BUG() in select_fallback_rq() at boot with isolcpus=domain on the boot CPU and CONFIG_CPUSETS=n

From: Peter Zijlstra

Date: Tue Nov 17 2026 - 10:02:38 EST


On Tue, Nov 17, 2026 at 09:48:17AM -0500, Mathieu Desnoyers wrote:
> 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.

Arguably, marking the boot cpu as isolated is asking for it. Is this
really worth fixing? Or should we look for a better failure message?