I just tried the firmwarekit, and here are the results, attached.
TYVM, thats a very useful tool.
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="results.css" type="text/css"?>
<results>
<test>
<id>apicedge</id>
<name>(experimental) APIC Edge/Level check</name>
<result>4</result>
<description>This test checks if legacy interrupts are edge and PCI interrupts are level</description>
<detail>
<summary>Non-Legacy interrupt 0 is incorrectly level triggered</summary>
<result>4</result>
<uri>interrupts://</uri>
<data> 0: 22353 XT-PIC-XT timer
</data>
</detail>
<detail>
<summary>Non-Legacy interrupt 1 is incorrectly level triggered</summary>
<result>4</result>
<uri>interrupts://</uri>
<data> 1: 9 XT-PIC-XT i8042
</data>
</detail>
<detail>
<summary>Non-Legacy interrupt 2 is incorrectly level triggered</summary>
<result>4</result>
<uri>interrupts://</uri>
<data> 2: 0 XT-PIC-XT cascade
</data>
</detail>
<detail>
<summary>Non-Legacy interrupt 8 is incorrectly level triggered</summary>
<result>4</result>
<uri>interrupts://</uri>
<data> 8: 0 XT-PIC-XT rtc
</data>
</detail>
<detail>
<summary>Non-Legacy interrupt 10 is incorrectly level triggered</summary>
<result>4</result>
<uri>interrupts://</uri>
<data> 10: 51 XT-PIC-XT ohci_hcd:usb1
</data>
</detail>
</test>
<test>
<id>microcode</id>
<name>Processor microcode update</name>
<result>4</result>
<description>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.</description>
<detail>
<summary>Cpu cpu0 has outdated microcode (version 34 while version 36 is available)</summary>
<result>4</result>
<uri></uri>
</detail>
</test>
<test>
<id>FADT</id>
<name>FADT test</name>
<result>4</result>
<description>verify FADT SCI_EN bit enabled or NOT.</description>
<detail>
<summary>E820: XSDT (0x2ed382e9) is not in reserved or ACPI memory!</summary>
<result>4</result>
<uri>e820://</uri>
</detail>
<detail>
<summary>Legacy mode, SCI_EN bit in PM1a_Control register is incorrectly Disabled</summary>
<result>4</result>
</detail>
<detail>
<summary>E820: XSDT (0x2ed382e9) is not in reserved or ACPI memory!</summary>
<result>4</result>
<uri>e820://</uri>
</detail>
</test>
<test>
<id>mtrr</id>
<name>MTRR validation</name>
<result>4</result>
<description>This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.</description>
<detail>
<summary>Memory range 0x100000 to 0xfdeffff (System RAM) has incorrect attribute default </summary>
<result>4</result>
<uri>mtrr://System RAM</uri>
<data>Memory range 0x100000 to 0xfdeffff (System RAM) has incorrect attribute default </data>
</detail>
</test>
<test>
<id>mcfg</id>
<name>MCFG PCI Express* memory mapped config space</name>
<result>4</result>
<description>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.</description>
<detail>
<summary>E820: XSDT (0x2ed382e9) is not in reserved or ACPI memory!</summary>
<result>4</result>
<uri>e820://</uri>
</detail>
<detail>
<summary>No MCFG ACPI table found. This table is required for PCI Express*.</summary>
<result>2</result>
</detail>
</test>
<test>
<id>edd</id>
<name>EDD Boot disk hinting</name>
<result>4</result>
<description>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.</description>
<detail>
<summary>Boot device 0x80 does not support EDD
</summary>
<result>4</result>
<uri></uri>
</detail>
</test>
<test>
<id>pciresource</id>
<name>Validate assigned PCI resources</name>
<result>4</result>
<description>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.</description>
<detail>
<summary>Device 0000:01:00.0 has incorrect resources</summary>
<result>4</result>
<uri>pci://0000:01:00.0</uri>
<data>PCI: Ignore bogus resource 6 [0:0] of 0000:01:00.0</data>
</detail>
</test>
<test>
<id>thermal_trip</id>
<name>ACPI passive thermal trip points</name>
<result>2</result>
<description>This test determines if the passive trip point works as expected.</description>
<detail>
<summary>Cannot test trip points without existing /proc/acpi/thermal_zone.</summary>
<result>2</result>
<uri></uri>
</detail>
</test>
<test>
<id>cpufreq</id>
<name>CPU frequency scaling tests</name>
<result>2</result>
<description>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
4) Is BIOS wrongly doing Sw_All P-state coordination across cores
5) Is BIOS wrongly doing Sw_Any P-state coordination across cores
</description>
<detail>
<summary>Frequency scaling not supported</summary>
<result>2</result>
<uri></uri>
</detail>
</test>
<test>
<id>virt</id>
<name>VT/VMX Virtualization extensions</name>
<result>1</result>
<description>This test checks if VT/VMX is set up correctly</description>
<detail>
<summary>Processor does not support Virtualization extensions</summary>
<result>1</result>
<uri></uri>
</detail>
</test>
<test>
<id>acpiinfo</id>
<name>General ACPI information</name>
<result>1</result>
<description>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.</description>
<detail>
<summary>DSDT was compiled by the Microsoft AML compiler</summary>
<result>1</result>
<data>ACPI: DSDT (v001 SiS 620 0x00001000 MSFT 0x0100000a) @ 0x00000000</data>
</detail>
</test>
<test>
<id>maxreadreq</id>
<name>PCI Express MaxReadReq tuning</name>
<result>0</result>
<description>This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices</description>
</test>
<test>
<id>os2gap</id>
<name>OS/2 memory hole test</name>
<result>0</result>
<description>This test checks if the OS/2 15Mb memory hole is absent</description>
</test>
<test>
<id>dmi</id>
<name>DMI information check</name>
<result>0</result>
<description>This test checks the DMI/SMBIOS tables for common errors.</description>
</test>
<test>
<id>chk_hpet</id>
<name>HPET configuration test</name>
<result>0</result>
<description>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.
</description>
</test>
<test>
<id>fan</id>
<name>Fan tests</name>
<result>0</result>
<description>This test reports how many fans there are in the system. It also checks for the states of the fan.</description>
<detail>
<summary>No fan information present</summary>
<result>1</result>
<uri></uri>
</detail>
</test>
<test>
<id>battery</id>
<name>Battery tests</name>
<result>0</result>
<description>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.</description>
<detail>
<summary>No battery information present</summary>
<result>1</result>
<uri></uri>
</detail>
</test>
<test>
<id>ethernet</id>
<name>Ethernet functionality</name>
<result>0</result>
<description>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.</description>
</test>
<test>
<id>acpicompile</id>
<name>DSDT AML verification</name>
<result>0</result>
<description>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.</description>
<detail>
<summary>Tested table DSDT.dsl</summary>
<result>0</result>
<uri></uri>
</detail>
<detail>
<summary>Tested _SUN ids; successfully found no duplicates</summary>
<result>0</result>
<uri></uri>
</detail>
</test>
</results>
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
