[Bug]: Linux kernel warning in CPU topology - [Silicon/Qemu/SbsaQemu] #752
Description
Is there an existing issue for this?
- I have searched existing issues
Bug Type
- Firmware
- Tool
- Unit Test
What packages are impacted?
Silicon/Qemu/SbsaQemu
Which targets are impacted by this bug?
No response
Current Behavior
When booting Linux, I see the following kernel warning
[ 0.202219] ------------[ cut here ]------------
[ 0.202311] WARNING: CPU: 0 PID: 1 at /kernel/sched/topology.c:2420
build_sched_domains+0x354/0x1190
[ 0.203028] Modules linked in:
[ 0.203643] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted
6.12.13-yocto-standard-00102-gc58d3ea5bbce #1
[ 0.203952] pstate: 01400009 (nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
[ 0.204144] pc : build_sched_domains+0x354/0x1190
[ 0.204204] lr : build_sched_domains+0x348/0x1190
[ 0.204261] sp : ffff80008003bce0
[ 0.204293] x29: ffff80008003bd60 x28: 0000000000000000 x27: 0000000000000000
[ 0.204511] x26: ffffc20695613cd0 x25: 0000000000000000 x24: ffffc20695b47098
[ 0.204616] x23: 0000000000000000 x22: 0000000000000001 x21: ffff00000210a638
[ 0.204719] x20: ffffc206955f9f70 x19: ffff0000020077e8 x18: 0000000000000001
[ 0.204822] x17: 4d52415120646574 x16: 6365746968637261 x15: 0000000000000000
[ 0.204925] x14: 0000000000000008 x13: 0000000000000400 x12: 0000000000000001
[ 0.205026] x11: 0000000000000002 x10: ffffc20695b47098 x9 : 0000000000000000
[ 0.205139] x8 : ffff000002178a48 x7 : 0000000000000000 x6 : 0000000000000001
[ 0.205236] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
[ 0.205332] x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000001
[ 0.205491] Call trace:
[ 0.205531] build_sched_domains+0x354/0x1190
[ 0.205611] sched_init_domains+0xb4/0xc8
[ 0.205686] sched_init_smp+0x48/0xd0
[ 0.205742] kernel_init_freeable+0x130/0x278
[ 0.205796] kernel_init+0x20/0x140
[ 0.205854] ret_from_fork+0x10/0x20
[ 0.205981] ---[ end trace 0000000000000000 ]---
Expected Behavior
No warning
Steps To Reproduce
Using Yocto Project (master branch), add the meta-arm layer (master branch)
modify the meta-arm/recipes-bsp/uefi/edk2-firmware_202408.bb to have
-SRCREV_edk2-platforms ?= "a3c898956a4d48dc5980336fa6ce6eeb23c4f72b"
+SRCREV_edk2-platforms ?= "2d66a9e048285af8ba4bfe4bdaab37a8e98288b3"
build for the sbsa-ref machine and boot the resulting build with
$ runqemu serialstdio slirp
or, with kas:
$ git clone https://git.yoctoproject.org/meta-arm
$ cd meta-arm
$ sed -i 's/a3c898956a4d48dc5980336fa6ce6eeb23c4f72b/2d66a9e048285af8ba4bfe4bdaab37a8e98288b3/g' meta-arm/recipes-bsp/uefi/edk2-firmware_202408.bb
$ kas build ci/sbsa-ref.yml:ci/testimage.yml
Build Environment
Yocto Project Walnascar (master branch) and the meta-arm layer (master branch)Version Information
Commit 2d66a9e048285af8ba4bfe4bdaab37a8e98288b3
Urgency
Low
Are you going to fix this?
Someone else needs to fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
With edk2 debug enabled, I captured the following topology information:
ProtectUefiImageCommon - 0x1EA98140
- 0x000001001E8AB000 - 0x0000000000007000
SetUefiImageMemoryAttributes - 0x000001001E8AB000 - 0x0000000000001000 (0x0000000000004008)
SetUefiImageMemoryAttributes - 0x000001001E8AC000 - 0x0000000000005000 (0x0000000000020008)
SetUefiImageMemoryAttributes - 0x000001001E8B1000 - 0x0000000000001000 (0x0000000000004008)
GetCpuCount: We have 4 cpus.
GetMpidr: MPIDR for CPU0: = 0
GetMpidr: MPIDR for CPU1: = 1
GetMpidr: MPIDR for CPU2: = 2
GetMpidr: MPIDR for CPU3: = 3
GetCpuCount: We have 4 cpus.
GetCpuTopology: CPU Topology: sockets: 1, clusters: 1, cores: 1, threads: 1
GetCpuCount: We have 4 cpus.
GetMemNodeCount: The number of the memory nodes is 1
GetCpuNumaNode: NUMA node for CPU0: = 0
GetCpuNumaNode: NUMA node for CPU1: = 0
GetCpuNumaNode: NUMA node for CPU2: = 0
GetCpuNumaNode: NUMA node for CPU3: = 0
GetMemInfo: NUMA node for System RAM:0 = 0x10000000000 - 0x1001FFFFFFF