I see quite a few errors in the dom0 kernel log:
Error #1:
[ 1.030499] CPU topo: Boot CPU APIC ID not the first enumerated APIC ID: 20 != 10
[ 1.030500] CPU topo: [Firmware Bug]: APIC enumeration order not specification compliant
[ 1.030517] CPU topo: CPU limit of 16 reached. Ignoring further CPUs
...
[ 1.030658] CPU topo: Max. logical packages: 1
[ 1.030659] CPU topo: Max. logical dies: 1
[ 1.030659] CPU topo: Max. dies per package: 1
[ 1.030664] CPU topo: Max. threads per core: 2
[ 1.030665] CPU topo: Num. cores per package: 10
[ 1.030666] CPU topo: Num. threads per package: 16
[ 1.030666] CPU topo: Allowing 16 present CPUs plus 0 hotplug CPUs
[ 1.030667] CPU topo: Rejected CPUs 6
The CPU has 22 threads but in dom0 I only see 16 and 6 have explicitly been rejected.
xl_info
output seems to confirm the problem:
nr_cpus : 16
max_cpu_id : 21
nr_nodes : 1
cores_per_socket : 1
threads_per_core : 16
Error #2:
[ 1.531804] ACPI BIOS Warning (bug): Incorrect checksum in table [BGRT] - 0x5D, should be 0x11 (20240827/utcksum-58)
I guess that’s harmless
Error #3:
[ 1.531982] [Firmware Bug]: CPU 0: APIC ID mismatch. CPUID: 0x0000 APIC: 0x0020
[ 0.008760] [Firmware Bug]: CPU 1: APIC ID mismatch. CPUID: 0x0001 APIC: 0x0021
[ 0.008760] [Firmware Bug]: CPU 1: APIC ID mismatch. Firmware: 0x0010 APIC: 0x0021
[ 1.558163] cpu 1 spinlock event irq 171
[ 0.008760] [Firmware Bug]: CPU 3: APIC ID mismatch. CPUID: 0x0003 APIC: 0x0029
[ 0.008760] [Firmware Bug]: CPU 3: APIC ID mismatch. Firmware: 0x0018 APIC: 0x0029
(lots more of there, timestamps are really non in chronological error)
[ 0.008760] [Firmware Bug]: CPU 11: APIC ID mismatch. CPUID: 0x000b APIC: 0x0006
[ 0.008760] [Firmware Bug]: CPU 11: APIC ID mismatch. Firmware: 0x0039 APIC: 0x0006
[ 1.563025] cpu 11 spinlock event irq 215
[ 1.563945] smp: Brought up 1 node, 16 CPUs
Mabe related to the kernel not recognizing all CPUs?
Error #4: Missing vpu Firmware
[ 4.605400] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2
[ 4.606833] intel_vpu 0000:00:0b.0: [drm] ivpu_hw_power_down(): NPU not idle during power down
[ 4.608200] intel_vpu 0000:00:0b.0: probe with driver intel_vpu failed with error -2
The Vision Processing Unit on the CPU needs firmware that seems to exist but isn’t available in fedora yet. I guess there is no downside of it since I don’t need it.
Error #5: NVMe failed to allocate host memory buffer
[ 4.617487] nvme 0000:01:00.0: platform quirk: setting simple suspend
[ 4.617500] nvme 0000:02:00.0: platform quirk: setting simple suspend
[ 4.618617] nvme nvme0: pci function 0000:01:00.0
[ 4.621010] nvme nvme1: pci function 0000:02:00.0
[ 4.628239] nvme nvme0: D3 entry latency set to 10 seconds
[ 4.634880] nvme nvme0: 16/0/0 default/read/poll queues
[ 4.641186] nvme nvme1: failed to allocate host memory buffer.
[ 4.651220] nvme0n1: p1 p2 p3 p4 p5 p6
[ 4.716788] nvme nvme1: 16/0/0 default/read/poll queues
This happens only on one of the 2 NVMes. It’s the brand new one that came with the laptop and hasn’t even been formatted yet. Qubes is running on nvme0 which is an old Samsung 990 Pro I transferred from another machine and doesn’t have this error.
Error seems harmless and at worst performance-degrading.
Error #6:
[ 14.876440] proc_thermal_pci 0000:00:04.0: error: proc_thermal_add, will continue
The device in question seems to be the Meteor Lake-P Dynamic Tuning Technology and should be supported from kernel 5.19 onwards:
00:04.0 Signal processing controller: Intel Corporation Device 7d03 (rev 04)
Error #7: DDR5 temperature sensor fail after resuming from S3
[ 1621.796873] spd5118 16-0050: Failed to write b = 0: -6
[ 1621.796889] spd5118 16-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 1621.796962] spd5118 16-0050: PM: failed to resume async: error -6
[ 1621.797139] spd5118 16-0052: Failed to write b = 0: -6
[ 1621.797148] spd5118 16-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 1621.797170] spd5118 16-0052: PM: failed to resume async: error -6
Coreboot Issue Tracker:
I’ve commented with these errors on this coreboot issue.