Attachment 155640 Details for Bug 229464 – Test results

Test results

results.txt (text/plain), 11.05 KB, created by Julian Sikorski on 2007-05-29 21:27:27 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Julian Sikorski

Created: 2007-05-29 21:27:27 UTC

Size: 11.05 KB

patch

obsolete

>-------------------------------------------------
>  Date: Tue May 29 18:13:26 2007                                       
>*                                               *
>* Firmwarekit (release 2.0)                     *
>* http://www.linuxfirmwarekit.org               *
>*                                               *
>*                                               *
>* For more information on test descriptions     *
>* and details on what the PASS/INFO/WARN/FAIL   *
>* results mean, go to: Documentation/TestsInfo. *
>*                                               *
>-------------------------------------------------
>
>SUMMARY:  4 Fails, 4 Warns, 13 Pass, 21 Total
>
>=================================================
>* Plugin name: dmi
>
>* Title: DMI information check
>* Description: This test checks the DMI/SMBIOS tables for common errors.
>* Result: FAIL
>================================================
>
>[FAIL]-No SMBIOS nor DMI entry point found.
>
>=================================================
>* Plugin name: chk_hpet
>
>* Title: HPET configuration test
>* 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.
>* Result: FAIL
>================================================
>
>[WARN]-HPET driver in the kernel is enabled, inaccurate results follow.
>
>[FAIL]-Mismatched HPET base between DSDT and the kernel
>
>Mismatched HPET base between DSDT (fed00000) and the kernel 10cd041)
>
>=================================================
>* Plugin name: mcfg
>
>* Title: MCFG PCI Express* memory mapped config space
>* 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.
>* Result: FAIL
>================================================
>
>[FAIL]-E820: MCFG mmio config space at 0xe0000000 is not reserved in the E820 table
>
>=================================================
>* Plugin name: cpufreq
>
>* Title: CPU frequency scaling tests
>* 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
>
>* Result: FAIL
>================================================
>
>[INFO]-4 CPU frequency steps supported
>
> Frequency | Speed 
>-----------+---------
>  2.05 Ghz | 100.0 %
>  1.72 Ghz |  83.4 %
>  1333 Mhz |  66.7 %
>  1000 Mhz |  50.1 %
>
>
>[FAIL]-Processors are set to SW_ANY
>
>[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ALL instead?
>
>
>[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ANY instead?
>
>
>=================================================
>* Plugin name: maxreadreq
>
>* Title: PCI Express MaxReadReq tuning
>* Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
>* Result: WARN
>================================================
>
>[WARN]-MaxReadReq for device pci://00:00:1b.0 is low (128)
>
>[WARN]-MaxReadReq for device pci://00:05:00.0 is low (128)
>
>=================================================
>* Plugin name: thermal_trip
>
>* Title: ACPI passive thermal trip points
>* Description: This test determines if the passive trip point works as expected.
>* Result: WARN
>================================================
>
>[WARN]-Zone TZ00 doesn't support passive trip point at all.
>
>[WARN]-Zone TZ01 doesn't support passive trip point at all.
>
>=================================================
>* Plugin name: FADT
>
>* Title: FADT test
>* Description: verify FADT SCI_EN bit enabled or NOT.
>* Result: WARN
>================================================
>
>[PASS]-ACPI mode, SCI_EN bit in PM1a_Control register is correctly enabled
>
>[WARN]-FADT field plvl3_lat has different 32/64 bit values
>
>FADT field plvl3_lat has value 39 in the 32 bit table and value 23 in the 64 bit table.
>
>=================================================
>* Plugin name: acpicompile
>
>* Title: DSDT AML verification
>* 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.
>* Result: WARN
>================================================
>
>[WARN]-Possible operator timeout is ignored
>
>Possible operator timeout is ignored
>At line #4659 of DSDT.dsl:
>
> |  Method (_EJ0, 1, NotSerialized)
> |  {
> |      If (Arg0)
> |      {
> |          Reset (DKRQ)
>>>>         Wait (DKRQ, 0x1400)
> |          Store (0x02, ^^^LPCB.EC0.DPPR)
> |          Sleep (0x14)
> |      }
> |  }
>
>
>[PASS]-Tested table DSDT.dsl
>
>=================================================
>* Plugin name: battery
>
>* Title: Battery tests
>* 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.
>* Result: INFO
>================================================
>
>[INFO]-Battery BAT0 is model PA3399U-2BAS/BRS and is currently charged
>
>=================================================
>* Plugin name: edd
>
>* Title: EDD Boot disk hinting
>* 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.
>* Result: INFO
>================================================
>
>[INFO]-device 80: The system boots from device 0000:00:1f.2 channel: 1 device: 0 
>
>
>[INFO]-device 80: The boot disk has Linux device name /dev/hda
>
>=================================================
>* Plugin name: ethernet
>
>* Title: Ethernet functionality
>* 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.
>* Result: INFO
>================================================
>
>[INFO]-Acquired ethernet link after 0 seconds
>
>[PASS]-Got a DHCP lease
>
>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:a0:d1:61:e9:6c
>Sending on   LPF/eth0/00:a0:d1:61:e9:6c
>Sending on   Socket/fallback
>DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
>DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
>DHCPOFFER from 10.1.45.100
>DHCPREQUEST on eth0 to 255.255.255.255 port 67
>DHCPACK from 10.1.45.100
>bound to 10.1.45.30 -- renewal in 125720 seconds.
>
>
>=================================================
>* Plugin name: acpiinfo
>
>* Title: General ACPI information
>* 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.
>* Result: INFO
>================================================
>
>[INFO]-DSDT was compiled by the Intel AML compiler
>
>ACPI: DSDT (v002 TOSINV CALISTGA 0x06040000 INTL 0x20050624) @ 0x00000000
>
>=================================================
>* Plugin name: SUN
>
>* Title: SUN duplicate test
>* Description: This makes sure that each SUN (Slot Unique Number) that is called in the DSDT through the Name() method is unique, no duplicates should be found.
>* Result: PASS
>================================================
>
>[PASS]-Tested _SUN ids, successfully found no duplicates
>
>=================================================
>* Plugin name: ebda
>
>* Title: EBDA region
>* Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
>* Result: PASS
>================================================
>
>[PASS]-EBDA region is correctly reserved in the E820 table.
>
>=================================================
>* Plugin name: virt
>
>* Title: VT/VMX Virtualization extensions
>* Description: This test checks if VT/VMX is set up correctly
>* Result: PASS
>================================================
>
>=================================================
>* Plugin name: apicedge
>
>* Title: (experimental) APIC Edge/Level check
>* Description: This test checks if legacy interrupts are edge and PCI interrupts are level
>* Result: PASS
>================================================
>
>=================================================
>* Plugin name: os2gap
>
>* Title: OS/2 memory hole test
>* Description: This test checks if the OS/2 15Mb memory hole is absent
>* Result: PASS
>================================================
>
>[PASS]-Successfully found no 15mb memory hole
>
>=================================================
>* Plugin name: microcode
>
>* Title: Processor microcode update
>* 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.
>* Result: PASS
>================================================
>
>=================================================
>* Plugin name: fan
>
>* Title: Fan tests
>* Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
>* Result: PASS
>================================================
>
>[PASS]-Fan FAN0 status is: on
>
>=================================================
>* Plugin name: mtrr
>
>* Title: MTRR validation
>* Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
>* Result: PASS
>================================================
>
>=================================================
>* Plugin name: pciresource
>
>* Title: Validate assigned PCI resources
>* 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.
>* Result: PASS
>================================================
>

Actions: View

Attachments on bug 229464: 155640 | 155641 | 155642 | 155643