apicedge
(experimental) APIC Edge/Level check
4
This test checks if legacy interrupts are edge and PCI interrupts are level
Non-Legacy interrupt 0 is incorrectly edge triggered
4
interrupts://
Non-Legacy interrupt 1 is incorrectly edge triggered
4
interrupts://
Non-Legacy interrupt 6 is incorrectly edge triggered
4
interrupts://
Non-Legacy interrupt 8 is incorrectly edge triggered
4
interrupts://
Non-Legacy interrupt 12 is incorrectly edge triggered
4
interrupts://
Non-Legacy interrupt 14 is incorrectly edge triggered
4
interrupts://
microcode
Processor microcode update
4
This test verifies if the firmware has put a recent version of the microcode into the processor at boot time. Recent microcode is important to have all the required features and errata updates for the processor.
Cpu cpu0 has outdated microcode (version 24 while version 37 is available)
4
chk_hpet
HPET configuration test
4
This test checks the HPET PCI BAR for each timer block in the timer.The base address is passed by the firmware via an ACPI table.IRQ routing and initialization is also verified by the test.
Failed to locate HPET base
4
The firmware AML code doesn't advertize the HPET base.
HPET might be disabled in the bios settings, or not supported by the platform.
edd
EDD Boot disk hinting
4
This test verifies if the BIOS directs the operating system on which storage device to use for booting (EDD information). This is important for systems that (can) have multiple disks. Linux distributions increasingly depend on this info to find out on which device to install the bootloader.
Boot device 0x80 does not support EDD
4
pciresource
Validate assigned PCI resources
4
This test is currently a placeholder and just checks the kernel log for complaints about PCI resource errors. In the future the idea is to actually perform a validation step on all PCI resources against a certain rule-set.
Device 0000:00:02.0 has incorrect resources
4
pci://0000:00:02.0
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
acpiinfo
General ACPI information
4
This test checks the output of the in-kernel ACPI CA against common error messages that indicate a bad interaction with the bios, including those that point at AML syntax errors.
DSDT was compiled by the Microsoft AML compiler
1
ACPI: DSDT (v001 DELL dt_ex 0x00001000 MSFT 0x0100000d) @ 0x00000000
_PSD domain information is corrupt!
4
dmesg://
acpi_processor-0742 [00] processor_preregister_: Error while parsing _PSD domain information. Assuming no coordination
thermal_trip
ACPI passive thermal trip points
2
This test determines if the passive trip point works as expected.
Zone * doesn't support passive trip point at all.
2
FADT
FADT test
2
verify FADT SCI_EN bit enabled or NOT.
ACPI table: expected 'XSDT', but got 'ÿ'
2
ACPI mode, SCI_EN bit in PM1a_Control register is correctly enabled
0
ACPI table: expected 'XSDT', but got 'ÿ'
2
mcfg
MCFG PCI Express* memory mapped config space
2
This test tries to validate the MCFG table by comparing the first 16 bytes in the MMIO mapped config space with the 'traditional' config space of the first PCI device (root bridge). The MCFG data is only trusted if it is marked reserved in the E820 table.
ACPI table: expected 'XSDT', but got 'ÿ'
2
No MCFG ACPI table found. This table is required for PCI Express*.
2
cpufreq
CPU frequency scaling tests
2
For each processor in the system, this test steps through the various frequency states (P-states) that the BIOS advertises for the processor. For each processor/frequency combination, a quick performance value is measured. The test then validates that:
1) Each processor has the same number of frequency states
2) Higher advertised frequencies have a higher performance
3) No duplicate frequency values are reported by the BIOS
Frequency scaling not supported
2
acpicompile
DSDT AML verification
2
This test first disassembles the DSDT of the BIOS, and then uses the IASL compiler from Intel to recompile the code. The IASL copiler is much stricter in detecting deviations from the ACPI specification and can find numerous defects that other AML compilers cannot find. Fixing these defects increases the probability that the BIOS will operate well with a variety of operating systems.
Unknown reserved name (_S5D) in \_SB.PCI0.PCI1._S5D
2
aml://\_SB_.PCI0.PCI1._S5D
Unknown reserved name (_S5D)
At \_SB.PCI0.PCI1._S5D
| {
| Return (0x02)
| }
| }
|
>>> Method (_S5D, 0, NotSerialized)
| {
| If (HACK ())
| {
| Return (0x03)
Tested table DSDT.dsl
0
The IASL compiler from Intel would save 245 bytes of space.
1
The existing code takes 9571 bytes
The IASL compiler from Intel uses 9326 bytes
This is a saving of 245 bytes.
ethernet
Ethernet functionality
1
This test is currently a placeholder for a more advanced ethernet test. Currently the only check performed is that a link is acquired within 45 seconds of enabling the interface. 45 seconds is close to the value most Linux distributions use as timeout value.
In the future the plan is to also perform actual data transfer tests as part of the ethernet test, to validate interrupt routing and other per-NIC behaviors.
Acquired ethernet link after 1 seconds
1
pci://0000:01:0c.0
Got a DHCP lease
0
Internet Systems Consortium DHCP Client V3.0.4-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:08:74:ea:88:2a
Sending on LPF/eth0/00:08:74:ea:88:2a
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.34 -- renewal in 107120 seconds.
maxreadreq
PCI Express MaxReadReq tuning
0
This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
os2gap
OS/2 memory hole test
0
This test checks if the OS/2 15Mb memory hole is absent
dmi
DMI information check
0
This test checks the DMI/SMBIOS tables for common errors.
fan
Fan tests
0
This test reports how many fans there are in the system. It also checks for the states of the fan.
mtrr
MTRR validation
0
This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
battery
Battery tests
0
This test reports which (if any) batteries there are in the system. In addition, for charging or discharging batteries, the test validates that the reported 'current capacity' properly increments/decrements in line with the charge/discharge state.
This test also stresses the entire battery state reporting codepath in the ACPI BIOS, and any warnings given by the ACPI interpreter will be reported.