From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
"Chen, Yu C" <yu.c.chen@intel.com>,
tim.c.chen@linux.intel.com
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
Ritesh Harjani <riteshh@linux.ibm.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-sched@vger.kernel.org
Subject: Re: [BUG] sched/cache: "Make LLC id continuous" causes NULL cpumask dereference in build_sched_domains on POWER9
Date: Thu, 28 May 2026 12:24:39 +0530 [thread overview]
Message-ID: <o6i06n2o.ritesh.list@gmail.com> (raw)
In-Reply-To: <51154de7-3700-4cb4-82f2-1b3a8fa427f7@linux.ibm.com>
Venkat Rao Bagalkote <venkat88@linux.ibm.com> writes:
> Greetings!!!
>
> I am seeing an early boot kernel panic due to NULL pointer dereference
> on a POWER9 (pSeries) system when testing linux-next (next-20260522).
>
>
> [ 0.039029] NIP [c000000000e58504] _find_first_bit+0x44/0x130
> [ 0.039043] LR [c000000000e58500] _find_first_bit+0x40/0x130
> [ 0.039054] Call Trace:
> [ 0.039060] [c0000000090e7b80] [c00000000416af20]
> schedutil_gov+0x0/0xa0 (unreliable)
> [ 0.039076] [c0000000090e7bc0] [c00000000038b3b8]
> build_sched_domains+0xad8/0xe50
> [ 0.039089] [c0000000090e7ce0] [c000000003045d78]
> sched_init_smp+0xa8/0x164
> [ 0.039102] [c0000000090e7d30] [c00000000300f374]
> kernel_init_freeable+0x250/0x370
> [ 0.039117] [c0000000090e7de0] [c000000000011f90] kernel_init+0x34/0x1e4
> [ 0.039129] [c0000000090e7e50] [c00000000000debc]
> ret_from_kernel_user_thread+0x14/0x1c
> [ 0.039142] ---- interrupt: 0 at 0x0
> [ 0.039150] Code: 41820090 7c0802a6 393cffff fbe10038 7c7f1b78
> fba10028 fbc10030 3bc00000 793dd7e2 f8010050 4bae6e9d 60000000
> <e93f0000> 2c290000 408200bc 283c0040
> [ 0.039196] ---[ end trace 0000000000000000 ]---
>
>
Well, I am hitting this on 7.1.0-rc5-next-20260526-00010-gbfac43765a97
with Qemu Pseries TCG power10/11.
[ 0.342868][ T1] smp: Bringing up secondary CPUs ...
[ 0.342868][ T1] smp: Bringing up secondary CPUs ...
[ 0.525419][ T1] smp: Brought up 1 node, 4 CPUs
[ 0.525419][ T1] smp: Brought up 1 node, 4 CPUs
[ 0.527992][ T1] numa: Node 0 CPUs: 0-3
[ 0.527992][ T1] numa: Node 0 CPUs: 0-3
[ 0.552787][ T1] BUG: Kernel NULL pointer dereference on read at 0x00000000
[ 0.552787][ T1] BUG: Kernel NULL pointer dereference on read at 0x00000000
[ 0.557446][ T1] Faulting instruction address: 0xc000000000fe3f1c
[ 0.557446][ T1] Faulting instruction address: 0xc000000000fe3f1c
cpu 0x0: Vector: 300 (Data Access) at [c000000006607800]
pc: c000000000fe3f1c: _find_first_bit+0xc/0xc0
lr: c00000000027b7d8: build_sched_domains+0xbb4/0x1938
sp: c000000006607ac0
msr: 8000000002009033
dar: 0
dsisr: 80000
current = 0xc000000006f9fb00
paca = 0xc000000005670000 irqmask: 0x03 irq_happened: 0x09
pid = 1, comm = swapper/0
Linux version 7.1.0-rc5-next-20260526-00010-gbfac43765a97-dirty (powerpc64le-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #19 SMP PREEMPT Thu May 28 12:29:51 IST 2026
enter ? for help
[link register ] c00000000027b7d8 build_sched_domains+0xbb4/0x1938
[c000000006607ac0] c00000000027b0a8 build_sched_domains+0x484/0x1938 (unreliable)
[c000000006607c20] c000000004053180 sched_init_domains+0x114/0x1cc
[c000000006607c70] c0000000040515e0 sched_init_smp+0x5c/0x17c
[c000000006607cc0] c000000004012888 kernel_init_freeable+0x258/0x790
[c000000006607dc0] c000000000011f3c kernel_init+0x34/0x268
[c000000006607e30] c00000000000debc ret_from_kernel_user_thread+0x14/0x1c
---- Exception: 0 at 0000000000000000
-ritesh
next prev parent reply other threads:[~2026-05-28 7:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 14:07 [BUG] sched/cache: "Make LLC id continuous" causes NULL cpumask dereference in build_sched_domains on POWER9 Venkat Rao Bagalkote
2026-05-25 15:35 ` Chen, Yu C
2026-05-25 16:16 ` K Prateek Nayak
2026-05-26 3:14 ` Chen, Yu C
2026-05-26 3:14 ` Srikar Dronamraju
2026-05-26 4:08 ` Chen, Yu C
2026-05-26 4:58 ` Srikar Dronamraju
2026-05-26 5:53 ` K Prateek Nayak
2026-05-26 14:08 ` [BUG] sched/cache: "Make LLC id continuous" causes NULL cpumask Chen Yu
2026-05-27 7:01 ` Shrikanth Hegde
2026-05-27 16:05 ` Chen, Yu C
2026-05-27 18:07 ` Shrikanth Hegde
2026-05-28 4:58 ` Shrikanth Hegde
2026-05-28 9:12 ` Chen, Yu C
2026-05-28 10:26 ` Shrikanth Hegde
2026-05-28 15:54 ` Srikar Dronamraju
2026-05-28 15:58 ` Srikar Dronamraju
2026-05-27 16:30 ` K Prateek Nayak
2026-05-26 5:24 ` [BUG] sched/cache: "Make LLC id continuous" causes NULL cpumask dereference in build_sched_domains on POWER9 Venkat Rao Bagalkote
2026-05-27 7:05 ` Shrikanth Hegde
2026-05-28 16:01 ` Srikar Dronamraju
2026-05-28 6:54 ` Ritesh Harjani [this message]
2026-05-28 16:06 ` Srikar Dronamraju
2026-05-28 11:27 ` Shrikanth Hegde
2026-05-28 13:21 ` Chen, Yu C
2026-05-28 15:06 ` Ritesh Harjani
2026-05-28 15:56 ` Srikar Dronamraju
2026-05-28 16:31 ` Shrikanth Hegde
2026-05-28 16:44 ` Srikar Dronamraju
2026-05-29 3:58 ` Shrikanth Hegde
2026-05-29 6:59 ` Venkat Rao Bagalkote
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=o6i06n2o.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=chleroy@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sched@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=riteshh@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=venkat88@linux.ibm.com \
--cc=yu.c.chen@intel.com \
/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