Public bug reported:
In ACPI spec 6.6
https://uefi.org/sites/default/files/resources/ACPI_Spec_6.6.pdf
Memory affinity structure field flags is defined as follow:
Field Bit-Length Bit-Offset Description
Specific-Purpose 29 3 Indicates whether this memory
is intended for specific-
purpose usage.
This field is functionally
analogous to the UEFI
EFI_MEMORY_SP attribute. See
the UEFI specification for
more details on this attribute.
This specific bits of field Flags is not reserved to zero bits and
should be handled according to ACPI and UEFI specs.
Following HIGH failure is seen due to FWTS consider these bits as
reserved to zero:
SRAT Memory Affinity Structure:
Type: 0x01
Length: 0x28
Proximity Domain: 0x00000004
Reserved: 0x0000
Base Address: 0x0000020400000000
Length: 0x0000002000000000
Reserved: 0x00000000
Flags: 0x0000000b
Reserved: 0x0000000000000000
FAILED [HIGH] SRATReservedBitsNonZero: Test 1, SRAT Memory Affinity Flags Bits
[31..3] must be zero, got 0x0000000b instead
================================================================================
0 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
================================================================================
FWTS expects the bit 3 to bit 31 of Memory Affinity Flags be zero, but bit 3 is
for SPM (Specific-Purpose).
This is defined in ACPI 6.6, so it a new bit and the tool is not following the
latest spec.
** Affects: fwts (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2138894
Title:
acpitables->srat: Flags Memory Affinity Structure bits 3-29 should not
be reserved..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/2138894/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs