search

Dasharo / dasharo-issues

The Dasharo issue tracker
https://dasharo.com/
25 stars 0 forks source link

bogus X2APIC entries in MADT ACPI table #1094

Open marmarek opened 1 month ago

marmarek commented 1 month ago

Component

Dasharo firmware

Device

NovaCustom NV4x 12th Gen

Dasharo version

1.7.2

Dasharo Tools Suite version

No response

Test case ID

No response

Brief summary

MADT table contains extra 8 entries all with the same APIC ID 0x17161514

How reproducible

always

How to reproduce

Boot Qubes and check xl dmesg. Or boot native Linux (but less detailed message)

Expected behavior

No errors

Actual behavior

Xen complains:

[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x10 beyond limit - processor ignored
[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x11 beyond limit - processor ignored
[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x12 beyond limit - processor ignored
[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x13 beyond limit - processor ignored
[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x14 beyond limit - processor ignored
[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x15 beyond limit - processor ignored
[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x16 beyond limit - processor ignored
[2024-10-16 12:42:21] (XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x17 beyond limit - processor ignored

Linux complains only with ACPI: x2apic entry ignored

Screenshots

No response

Additional context

No response

Solutions you've tried

No response

royger commented 1 month ago

APIC.txt Attaching the disassembly of the MADT table. Note the bogus trailing x2APIC entries all with the same (very high) x2APIC ID.

miczyg1 commented 1 month ago

It was already fixed by us not so long ago: https://github.com/Dasharo/coreboot/commit/12676bdfe562d082663c2f12d625717cef046865

However, there was no new release for NV4x since January, and the fix landed later. Not sure if there are any plans on new firmware release for NV4x 12th gen, so this issue may be never be resolved.

The MTL laptops are unaffected, because they use newer coreboot base and the fix was already upstream.