Results generated by fwts: Version V14.01.01 (2014-01-24 03:21:43). Some of this work - Copyright (c) 1999 - 2014, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2014, Canonical. This test run on 25/02/14 at 03:33:53 on host Linux 201307-13944 3.11.0-15-generic #25~precise1-Ubuntu SMP Thu Jan 30 17:39:31 UTC 2014 x86_64. Command: "fwts -q --stdout-summary -r hibernate-single --s4-device-check --s4-device-check-delay 45 --s4-sleep-delay 120 s4". Running tests: s4. s4: S4 hibernate/resume test. -------------------------------------------------------------------------------- Test 1 of 1: S4 hibernate/resume test. Defaulted to run 1 test, run --s4-multiple=N to run more S4 cycles S4 cycle 1 of 1 Video configurations differ, before: PCI: 0000:00:02.0, VID: 86:56, Class: 03:00 (VGA/8512 compatible controller) Config: 0000: 86 80 56 01 07 04 90 00 09 00 00 03 00 00 00 00 ..V............. 0010: 04 00 00 f3 00 00 00 00 0c 00 00 d0 00 00 00 00 ................ 0020: 01 40 00 00 00 00 00 00 00 00 00 00 aa 17 14 50 .@.............P 0030: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00 ................ PCI: 0000:01:00.0, VID: de:40, Class: 03:02 (3D controller) Config: 0000: de 10 40 11 03 00 10 00 a1 00 02 03 10 00 00 00 ..@............. 0010: 00 00 00 f2 0c 00 00 e0 00 00 00 00 0c 00 00 f0 ................ 0020: 00 00 00 00 01 30 00 00 00 00 00 00 00 00 00 00 .....0.......... 0030: 00 00 f8 ff 60 00 00 00 00 00 00 00 0b 01 00 00 ....`........... versus after: PCI: 0000:00:02.0, VID: 86:56, Class: 03:00 (VGA/8512 compatible controller) Config: 0000: 86 80 56 01 07 04 90 00 09 00 00 03 00 00 00 00 ..V............. 0010: 04 00 00 f3 00 00 00 00 0c 00 00 d0 00 00 00 00 ................ 0020: 01 40 00 00 00 00 00 00 00 00 00 00 aa 17 14 50 .@.............P 0030: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00 ................ PCI: 0000:01:00.0, VID: de:40, Class: 03:02 (3D controller) Config: 0000: de 10 40 11 03 00 10 00 a1 00 02 03 10 00 00 00 ..@............. 0010: 00 00 00 f2 0c 00 00 e0 00 00 00 00 0c 00 00 f0 ................ 0020: 00 00 00 00 01 30 00 00 00 00 00 00 aa 17 14 50 .....0.........P 0030: 00 00 f8 ff 60 00 00 00 00 00 00 00 0b 01 00 00 ....`........... FAILED [HIGH] DevConfigDiffAfterS4: Test 1, Found 1 differences in device configuation during S4 cycle. PASSED: Test 1, No kernel log errors detected. PASSED: Test 1, No PM related hibernate issues detected. Found 1 device errors. PASSED: Test 1, No kernel oopses detected. PASSED: Test 1, No kernel WARN_ON warnings detected. Found 1 errors and 0 oopses doing 1 hibernate/resume cycle(s). ================================================================================ 4 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ 4 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. Test Failure Summary ================================================================================ Critical failures: NONE High failures: 1 s4: Found 1 differences in device configuation during S4 cycle. Medium failures: NONE Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---------------+-----+-----+-----+-----+-----+-----+ s4 | 4| 1| | | | | ---------------+-----+-----+-----+-----+-----+-----+ Total: | 4| 1| 0| 0| 0| 0| ---------------+-----+-----+-----+-----+-----+-----+ Results generated by fwts: Version V14.01.01 (2014-01-24 03:21:43). Some of this work - Copyright (c) 1999 - 2014, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2014, Canonical. This test run on 25/02/14 at 04:05:34 on host Linux 201307-13944 3.11.0-17-generic #31~precise1-Ubuntu SMP Tue Feb 4 21:25:43 UTC 2014 x86_64. Command: "fwts -q --stdout-summary -r hibernate-single --s4-device-check --s4-device-check-delay 45 --s4-sleep-delay 120 s4". Running tests: s4. s4: S4 hibernate/resume test. -------------------------------------------------------------------------------- Test 1 of 1: S4 hibernate/resume test. Defaulted to run 1 test, run --s4-multiple=N to run more S4 cycles S4 cycle 1 of 1 PASSED: Test 1, No kernel log errors detected. PASSED: Test 1, No PM related hibernate issues detected. PASSED: Test 1, No device errors detected. PASSED: Test 1, No kernel oopses detected. PASSED: Test 1, No kernel WARN_ON warnings detected. PASSED: Test 1, Found no errors and no oopses doing 1 hibernate/resume cycle(s). ================================================================================ 6 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ 6 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. Test Failure Summary ================================================================================ Critical failures: NONE High failures: NONE Medium failures: NONE Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---------------+-----+-----+-----+-----+-----+-----+ s4 | 6| | | | | | ---------------+-----+-----+-----+-----+-----+-----+ Total: | 6| 0| 0| 0| 0| 0| ---------------+-----+-----+-----+-----+-----+-----+ Results generated by fwts: Version V14.01.01 (2014-01-24 03:21:43). Some of this work - Copyright (c) 1999 - 2014, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2014, Canonical. This test run on 25/02/14 at 04:28:52 on host Linux 201307-13944 3.11.0-17-generic #31~precise1-Ubuntu SMP Tue Feb 4 21:25:43 UTC 2014 x86_64. Command: "fwts -q --stdout-summary -r hibernate-single --s4-device-check --s4-device-check-delay 45 --s4-sleep-delay 120 s4". Running tests: s4. s4: S4 hibernate/resume test. -------------------------------------------------------------------------------- Test 1 of 1: S4 hibernate/resume test. Defaulted to run 1 test, run --s4-multiple=N to run more S4 cycles S4 cycle 1 of 1 PASSED: Test 1, No kernel log errors detected. PASSED: Test 1, No PM related hibernate issues detected. PASSED: Test 1, No device errors detected. PASSED: Test 1, No kernel oopses detected. PASSED: Test 1, No kernel WARN_ON warnings detected. PASSED: Test 1, Found no errors and no oopses doing 1 hibernate/resume cycle(s). ================================================================================ 6 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ 6 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. Test Failure Summary ================================================================================ Critical failures: NONE High failures: NONE Medium failures: NONE Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---------------+-----+-----+-----+-----+-----+-----+ s4 | 6| | | | | | ---------------+-----+-----+-----+-----+-----+-----+ Total: | 6| 0| 0| 0| 0| 0| ---------------+-----+-----+-----+-----+-----+-----+ Results generated by fwts: Version V14.01.01 (2014-01-24 03:21:43). Some of this work - Copyright (c) 1999 - 2014, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2014, Canonical. This test run on 25/02/14 at 05:24:40 on host Linux 201307-13944 3.11.0-17-generic #31~precise1-Ubuntu SMP Tue Feb 4 21:25:43 UTC 2014 x86_64. Command: "fwts -q --stdout-summary -r hibernate-single --s4-device-check". Running tests: version bios_info oops klog mtrr acpiinfo securebootcert csm maxreadreq crs aspm hpet_check dmicheck microcode msr nx cpufreq maxfreq virt pnp pciirq os2gap mpcheck hda_audio ebda bios32 apicedge wmi wakealarm syntaxcheck pcc osilinux method mcfg fan fadt dmar cstates checksum autobrightness apicinstance acpitables. version: Gather kernel system information. -------------------------------------------------------------------------------- Test 1 of 4: Gather kernel signature. Signature: Ubuntu 3.11.0-17.31~precise1-generic 3.11.10.3 Test 2 of 4: Gather kernel system information. Kernel Version: Linux version 3.11.0-17-generic (buildd@toyol) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #31~precise1-Ubuntu SMP Tue Feb 4 21:25 :43 UTC 2014 Test 3 of 4: Gather kernel boot command line. Kernel boot command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=934b233d-ad6e-4ca0-b2cf-45c1ba0dcc75 ro quiet splash initcall_debug vt.handoff=7 Test 4 of 4: Gather ACPI driver version. ACPI Version: 20130517 ================================================================================ 0 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 4 info only. ================================================================================ bios_info: Gather BIOS DMI information. -------------------------------------------------------------------------------- Test 1 of 1: Gather BIOS DMI information BIOS Vendor : LENOVO BIOS Version : HBET20X1(1.04) BIOS Release Date : 07/11/2013 Board Name : INVALID Board Serial # : INVALID Board Version : Not Available Board Asset Tag : Not Available Chassis Serial # : INVALID Chassis Type : 10 Chassis Vendor : LENOVO Chassis Version : Not Available Chassic Asset Tag : No Asset Information Product Name : INVALID Product Serial # : INVALID Product Version : Lenovo System Vendor : LENOVO ================================================================================ 0 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 1 info only. ================================================================================ oops: Scan kernel log for Oopses. -------------------------------------------------------------------------------- Test 1 of 1: Kernel log oops check. PASSED: Test 1, Found no oopses in kernel log. PASSED: Test 1, Found no WARN_ON warnings in kernel log. ================================================================================ 2 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ klog: Scan kernel log for errors and warnings. -------------------------------------------------------------------------------- Test 1 of 1: Kernel log error check. Kernel message: [ 0.002640] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' ADVICE: This is not exactly a failure but a warning from the kernel. The MSR_IA32_ENERGY_PERF_BIAS was initialized and defaulted to a high performance bias setting. The kernel has detected this and changed it down to a 'normal' bias setting. FAILED [HIGH] KlogAcpiNoHandlerForRegion: Test 1, HIGH Kernel message: [ 0.106760] ACPI Error: No handler for Region [ECOR] (ffff8801294d4cf0) [EmbeddedControl] (20130517/evregion-162) ADVICE: ACPI attempted to read or write to a region however the ACPI driver does not have a handler implemented for this particular region space. The read/write will fail and undefined behaviour will occur. FAILED [HIGH] KlogAcpiKlogRegionNoHandler: Test 1, HIGH Kernel message: [ 0.106765] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20130517 /exfldio-305) Message repeated 1 times. ADVICE: An access (read or write) to an operation region has been attempted and a region handler for this has not been implemented, this may need to be implemented to provide the expected behaviour. See acpi_ex_access_region(). FAILED [HIGH] KlogAcpiObjectDoesNotExist: Test 1, HIGH Kernel message: [ 0.106769] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.H_EC._REG] (Node ffff8801294e2050), AE_NOT_EXIST (20130517/psparse-536) ADVICE: The ACPI interpreter failed to execute or parse some AML because a object or control did not exist. This normally occurs because of buggy firmware and may lead to unexpected behaviour or loss of functionality. Kernel message: [ 0.119433] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored ADVICE: This is not exactly a failure mode but a warning from the kernel. The _OSI() method has implemented a match to the 'Linux' query in the DSDT and this is redundant because the ACPI driver matches onto the Windows _OSI strings by default. FAILED [HIGH] KlogAcpiSleepStateEvalFailed: Test 1, HIGH Kernel message: [ 0.340686] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571) ADVICE: Failed to evaluate _Sx namespace object that contains the register values for the sleep state. FAILED [HIGH] KlogAcpiSleepStateEvalFailed: Test 1, HIGH Kernel message: [ 0.340694] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571) ADVICE: Failed to evaluate _Sx namespace object that contains the register values for the sleep state. FAILED [HIGH] KlogOscInvalidUuid: Test 1, HIGH Kernel message: [ 0.365643] \_SB_.PCI0:_OSC invalid UUID Message repeated 1 times. ADVICE: The _OSC method indicates it has been passed an invalid UUID, see section 6.2.10 _OSC (Operating System Capabilities) of the ACPI specification for more details. Note that it has been observed on some systems that this error is returned because the _OSC has evaluated incorrectly and it returns with an incorrect error setting the OSC invalid UUID error bit. FAILED [HIGH] KlogAcpiNoHandlerForRegion: Test 1, HIGH Kernel message: [ 0.821788] ACPI Error: No handler for Region [ECRM] (ffff880129068510) [EmbeddedControl] (20130517/evregion-162) ADVICE: ACPI attempted to read or write to a region however the ACPI driver does not have a handler implemented for this particular region space. The read/write will fail and undefined behaviour will occur. FAILED [HIGH] KlogAcpiObjectDoesNotExist: Test 1, HIGH Kernel message: [ 0.821798] ACPI Error: Method parse/execution failed [\_TZ_.MDEC] (Node ffff8801294e4f50), AE_NOT_EXIST (20130517/psparse-536) ADVICE: The ACPI interpreter failed to execute or parse some AML because a object or control did not exist. This normally occurs because of buggy firmware and may lead to unexpected behaviour or loss of functionality. FAILED [HIGH] KlogAcpiObjectDoesNotExist: Test 1, HIGH Kernel message: [ 0.821805] ACPI Error: Method parse/execution failed [\_TZ_.TZS0._SCP] (Node ffff8801294e5000), AE_NOT_EXIST (20130517/psparse-536) ADVICE: The ACPI interpreter failed to execute or parse some AML because a object or control did not exist. This normally occurs because of buggy firmware and may lead to unexpected behaviour or loss of functionality. FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 6.553320] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20130517/utaddress-251) ADVICE: A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). One can specify kernel boot parameter acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered. FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 6.553334] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20130517/utaddress-251) ADVICE: A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). One can specify kernel boot parameter acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered. FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 6.553339] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 (20130517/utaddress-251) ADVICE: A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). One can specify kernel boot parameter acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered. FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 6.553342] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 (20130517/utaddress-251) ADVICE: A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). One can specify kernel boot parameter acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered. FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 6.553347] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20130517/utaddress-251) ADVICE: A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). One can specify kernel boot parameter acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered. FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 6.553351] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 (20130517/utaddress-251) ADVICE: A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). One can specify kernel boot parameter acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered. FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 6.553354] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 (20130517/utaddress-251) ADVICE: A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). One can specify kernel boot parameter acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered. FAILED [LOW] KlogAcpiSystemIOConflictLpcIchWatchDogTimer: Test 1, LOW Kernel message: [ 6.553359] lpc_ich: Resource conflict(s) found affecting gpio_ich ADVICE: A resource conflict has occurred between ACPI OperationRegions and the same I/O region used by the lpc_ich driver for the General Purpose I/O (GPIO) region. Sometimes this GPIO region is used by the firmware for rfkill or LED controls or very rarely for the Embedded Controller System Control Interrupt. This may require deeper inspection to check if the conflict will lead to any real issues. However, in the vast majority of cases this warning can be ignored as no harm will occur. FAILED [HIGH] KlogAcpiDodEvalFailed: Test 1, HIGH Kernel message: [ 9.164754] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20130517/video-1264) ADVICE: The ACPI driver failed to enumerate the ACPI video devices because the _DOD (Enumerate All Devices Attached to the Display Adapter) control failed. This may explain why the video device is not functioning correctly. Found 18 unique errors in kernel log. ================================================================================ 0 passed, 18 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ mtrr: MTRR tests. -------------------------------------------------------------------------------- MTRR overview ------------- Reg 0: 0x00000000ffc00000 - 0x0000000100000000 ( 4 MB) Write-Protect Reg 1: 0x0000000000000000 - 0x0000000080000000 ( 2048 MB) Write-Back Reg 2: 0x0000000080000000 - 0x00000000c0000000 ( 1024 MB) Write-Back Reg 3: 0x00000000c0000000 - 0x00000000d0000000 ( 256 MB) Write-Back Reg 4: 0x00000000cc000000 - 0x00000000d0000000 ( 64 MB) Uncached Reg 5: 0x00000000cb000000 - 0x00000000cc000000 ( 16 MB) Uncached Reg 6: 0x0000000100000000 - 0x0000000120000000 ( 512 MB) Write-Back Reg 7: 0x0000000120000000 - 0x0000000130000000 ( 256 MB) Write-Back Reg 8: 0x000000012f800000 - 0x0000000130000000 ( 8 MB) Uncached Reg 9: 0x000000012f600000 - 0x000000012f800000 ( 2 MB) Uncached Test 1 of 3: Validate the kernel MTRR IOMEM setup. PASSED: Test 1, Memory ranges seem to have correct attributes. Test 2 of 3: Validate the MTRR setup across all processors. PASSED: Test 2, All processors have the a consistent MTRR setup. Test 3 of 3: Test for AMD MtrrFixDramModEn being cleared by the BIOS. SKIPPED: Test 3, CPU is not an AMD, cannot test. ================================================================================ 2 passed, 0 failed, 0 warning, 0 aborted, 1 skipped, 0 info only. ================================================================================ acpiinfo: General ACPI information test. -------------------------------------------------------------------------------- Test 1 of 3: Determine Kernel ACPI version. Kernel ACPICA driver version: 20130517, supports ACPI 5.0 Test 2 of 3: Determine machine's ACPI version. FACP ACPI Version: 5.0 Test 3 of 3: Determine AML compiler. Determine the compiler used to generate the ACPI AML in the DSDT and SSDT. Table DSDT, OEM LENOVO, created with INTL (Intel) compiler. Table SSDT0, OEM LENOVO, created with INTL (Intel) compiler. Table SSDT1, OEM PmRef, created with INTL (Intel) compiler. Table SSDT2, OEM PmRef, created with INTL (Intel) compiler. Table SSDT3, OEM NvORef, created with INTL (Intel) compiler. ================================================================================ 0 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 3 info only. ================================================================================ securebootcert: UEFI secure boot test. -------------------------------------------------------------------------------- Cannot detect any UEFI firmware. Aborted. Aborted test, initialisation failed. ================================================================================ 0 passed, 0 failed, 0 warning, 1 aborted, 0 skipped, 0 info only. ================================================================================ csm: UEFI Compatibility Support Module test. -------------------------------------------------------------------------------- Test 1 of 1: UEFI Compatibility Support Module test. Checking for UEFI Compatibility Support Module (CSM) Int 10h jumps to 0xc0014 in option ROM at: 0xc0000..0xcf000 No CSM: Legacy BIOS firmware has video option ROM with Int 10h support. ================================================================================ 0 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 1 info only. ================================================================================ maxreadreq: Test firmware has set PCI Express MaxReadReq to a higher value on non-motherboard devices. -------------------------------------------------------------------------------- Test 1 of 1: Test firmware settings MaxReadReq for PCI Express devices. PASSED: Test 1, All devices have MaxReadReq set > 128. ================================================================================ 1 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ crs: Test PCI host bridge configuration using _CRS. -------------------------------------------------------------------------------- Test 1 of 1: Test PCI host bridge configuration using _CRS. PASSED: Test 1, The kernel has detected a BIOS newer than the end of 2007 (7/11 /2013) and has assumed that your BIOS can correctly specify the host bridge MMIO aperture using _CRS. If this does not work correctly you can override this by booting with "pci=nocrs". ================================================================================ 1 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ aspm: PCIe ASPM test. -------------------------------------------------------------------------------- Test 1 of 2: PCIe ASPM ACPI test. PCIe ASPM is not controlled by Linux kernel. ADVICE: BIOS reports that Linux kernel should not modify ASPM settings that BIOS configured. It can be intentional because hardware vendors identified some capability bugs between the motherboard and the add-on cards. Test 2 of 2: PCIe ASPM registers test. WARNING: Test 2, RP 00h:01h.00h L0s not enabled. WARNING: Test 2, Device 01h:00h.00h L0s not enabled. ADVICE: The ASPM L0s low power Link state is optimized for short entry and exit latencies, while providing substantial power savings. Disabling L0s of a PCIe device may increases power consumption, and will impact the battery life of a mobile system. PASSED: Test 2, PCIe ASPM setting matched was matched. WARNING: Test 2, RP 00h:1Ch.01h L0s not enabled. ADVICE: The ASPM L0s low power Link state is optimized for short entry and exit latencies, while providing substantial power savings. Disabling L0s of a PCIe device may increases power consumption, and will impact the battery life of a mobile system. PASSED: Test 2, PCIe ASPM setting matched was matched. WARNING: Test 2, RP 00h:1Ch.03h L0s not enabled. WARNING: Test 2, Device 04h:00h.00h L0s not enabled. ADVICE: The ASPM L0s low power Link state is optimized for short entry and exit latencies, while providing substantial power savings. Disabling L0s of a PCIe device may increases power consumption, and will impact the battery life of a mobile system. PASSED: Test 2, PCIe ASPM setting matched was matched. ================================================================================ 3 passed, 0 failed, 5 warnings, 0 aborted, 0 skipped, 0 info only. ================================================================================ hpet_check: HPET configuration tests. -------------------------------------------------------------------------------- Test 1 of 4: Test HPET base in kernel log. 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. PASSED: Test 1, Found HPET base 0xfed00000 in kernel log. Test 2 of 4: Test HPET base in HPET table. Hardware ID of Event Block: PCI Vendor ID : 0x8086 Legacy IRQ Routing Capable : 1 COUNT_SIZE_CAP counter size: 1 Number of comparitors : 3 Hardwre Revision ID : 0x1 Lower 32 bit base Address : 0xfed00000 Address Space ID : 0x0 Register Bit Width : 0x0 Register Bit Offset : 0x0 Address Width : 0x0 HPET sequence number : 0x0 Minimum clock tick : 0x80 Page Protection : 0x0 (No guaranteed protection) OEM attributes : 0x0 PASSED: Test 2, HPET looks sane. Test 3 of 4: Test HPET base in DSDT and/or SSDT. PASSED: Test 3, HPET base matches that between DSDT and the kernel (0xfed00000). Test 4 of 4: Test HPET configuration. PASSED: Test 4, Vendor ID looks sane: 0x8086. PASSED: Test 4, Valid clock period 69841279. ================================================================================ 5 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ dmicheck: DMI/SMBIOS table tests. -------------------------------------------------------------------------------- Test 1 of 2: Find and test SMBIOS Table Entry Point. This test tries to find and sanity check the SMBIOS data structures. PASSED: Test 1, Found SMBIOS Table Entry Point at 0xf00e0 SMBIOS Entry Point Structure: Anchor String : _SM_ Checksum : 0x66 Entry Point Length : 0x1f Major Version : 0x02 Minor Version : 0x07 Maximum Struct Size : 0x14 Entry Point Revision : 0x00 Formatted Area : 0x00 0x00 0x00 0x00 0x00 Intermediate Anchor : _DMI_ Intermediate Checksum : 0x62 Structure Table Length : 0x0979 Structure Table Address: 0xcae37000 # of SMBIOS Structures : 0x0040 SBMIOS BCD Revision : 27 PASSED: Test 1, SMBIOS Table Entry Point Checksum is valid. PASSED: Test 1, SMBIOS Table Entry Point Length is valid. PASSED: Test 1, SMBIOS Table Entry Intermediate Anchor String _DMI_ is valid. PASSED: Test 1, SMBIOS Table Entry Point Intermediate Checksum is valid. PASSED: Test 1, SMBIOS Table Entry Structure Table Address and Length looks valid. Test 2 of 2: Test DMI/SMBIOS tables for errors. PASSED: Test 2, Entry @ 0xcae37000 'Unknown (Type 134)' FAILED [LOW] DMISerialNumber: Test 2, String index 0x03 in table entry 'Processor Information (Type 4)' @ 0xcae3702a, field 'Serial Number', offset 0x20 has a default value 'To Be Filled By O.E.M.' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. FAILED [LOW] DMISerialNumber: Test 2, String index 0x05 in table entry 'Processor Information (Type 4)' @ 0xcae3702a, field 'Asset Tag', offset 0x21 has a default value 'To Be Filled By O.E.M.' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. FAILED [LOW] DMISerialNumber: Test 2, String index 0x06 in table entry 'Processor Information (Type 4)' @ 0xcae3702a, field 'Part Number', offset 0x22 has a default value 'To Be Filled By O.E.M.' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.5 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). PASSED: Test 2, Entry @ 0xcae370e9 'Cache Information (Type 7)' PASSED: Test 2, Entry @ 0xcae37106 'Cache Information (Type 7)' PASSED: Test 2, Entry @ 0xcae37123 'Cache Information (Type 7)' PASSED: Test 2, Entry @ 0xcae37140 'Cache Information (Type 7)' PASSED: Test 2, Entry @ 0xcae3715d 'Unknown (Type 129)' PASSED: Test 2, Entry @ 0xcae3717e 'Unknown (Type 131)' PASSED: Test 2, Entry @ 0xcae371c0 'Physical Memory Array (Type 16)' FAILED [LOW] DMIAssetTag: Test 2, String index 0x05 in table entry 'Memory Device (Type 17)' @ 0xcae371d9, field 'Asset Tag', offset 0x19 has a default value '9876543210' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.18 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). FAILED [LOW] DMIAssetTag: Test 2, String index 0x03 in table entry 'Memory Device (Type 17)' @ 0xcae37240, field 'Asset Tag', offset 0x19 has a default value '9876543210' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.18 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). PASSED: Test 2, Entry @ 0xcae37284 'Memory Device Mapped Address (Type 20)' PASSED: Test 2, Entry @ 0xcae372a9 'Memory Array Mapped Address (Type 19)' PASSED: Test 2, Entry @ 0xcae372ca 'BIOS Information (Type 0)' PASSED: Test 2, Entry @ 0xcae37304 'System Information (Type 1)' FAILED [MEDIUM] DMISerialNumber: Test 2, String index 0x03 in table entry 'Base Board Information (Type 2)' @ 0xcae37353, field 'Version', offset 0x06 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless. Note that the kernel uses this field so it probably should be corrected to ensure the kernel is using sane values. FAILED [MEDIUM] DMISerialNumber: Test 2, String index 0x05 in table entry 'Base Board Information (Type 2)' @ 0xcae37353, field 'Asset Tag', offset 0x08 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless. Note that the kernel uses this field so it probably should be corrected to ensure the kernel is using sane values. FAILED [LOW] DMISerialNumber: Test 2, String index 0x06 in table entry 'Base Board Information (Type 2)' @ 0xcae37353, field 'Location In Chassis', offset 0x0a has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.3 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). FAILED [MEDIUM] DMISerialNumber: Test 2, String index 0x02 in table entry 'Chassis Information (Type 3)' @ 0xcae373a5, field 'Version', offset 0x06 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless. Note that the kernel uses this field so it probably should be corrected to ensure the kernel is using sane values. FAILED [MEDIUM] DMIAssetTag: Test 2, String index 0x04 in table entry 'Chassis Information (Type 3)' @ 0xcae373a5, field 'Asset Tag', offset 0x08 has a default value 'No Asset Information' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless. Note that the kernel uses this field so it probably should be corrected to ensure the kernel is using sane values. ADVICE: It may be worth checking against section 7.4 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae373fb, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae37424, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). PASSED: Test 2, Entry @ 0xcae3744d 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae37479 'Inactive (Type 126)' FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae374a5, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). PASSED: Test 2, Entry @ 0xcae374cc 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae374f3 'Inactive (Type 126)' FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae3751b, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). PASSED: Test 2, Entry @ 0xcae3753c 'Inactive (Type 126)' FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae3755a, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae37578, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae37596, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). FAILED [LOW] DMISerialNumber: Test 2, String index 0x01 in table entry 'Port Connector Information (Type 8)' @ 0xcae375b4, field 'Internal Reference Designator', offset 0x04 has a default value 'Not Available' and probably has not been updated by the BIOS vendor. ADVICE: The DMI table contains data which is clearly been left in a default setting and not been configured for this machine. Somebody has probably forgotten to define this field and it basically means this field is effectively useless, however the kernel does not use this data so the issue is fairly low. ADVICE: It may be worth checking against section 7.9 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards /smbios). PASSED: Test 2, Entry @ 0xcae375d2 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae375f0 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae3760e 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae3762c 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae3764a 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae37668 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae37687 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae376a6 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae376c7 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae376e5 'System Slot Information (Type 9)' PASSED: Test 2, Entry @ 0xcae37708 'System Slot Information (Type 9)' PASSED: Test 2, Entry @ 0xcae3772a 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae3774b 'On Board Devices (Type 10)' PASSED: Test 2, Entry @ 0xcae37771 'System Configuration Options (Type 12)' PASSED: Test 2, Entry @ 0xcae37778 'BIOS Language Information (Type 13)' PASSED: Test 2, Entry @ 0xcae377b2 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae377ce 'Inactive (Type 126)' PASSED: Test 2, Entry @ 0xcae377ea '32-bit Memory Error Information (Type 18)' PASSED: Test 2, Entry @ 0xcae37803 'Built-in Pointing Device (Type 21)' PASSED: Test 2, Entry @ 0xcae3780c 'Built-in Pointing Device (Type 21)' PASSED: Test 2, Entry @ 0xcae37815 'Unknown (Type 131)' PASSED: Test 2, Entry @ 0xcae3783b 'Unknown (Type 135)' PASSED: Test 2, Entry @ 0xcae37887 'Unknown (Type 133)' PASSED: Test 2, Entry @ 0xcae3789c 'Unknown (Type 135)' PASSED: Test 2, Entry @ 0xcae378a8 'System Event Log (Type 15)' PASSED: Test 2, Entry @ 0xcae378fb 'Hardware Security (Type 24)' PASSED: Test 2, Entry @ 0xcae37902 'Unknown (Type 132)' PASSED: Test 2, Entry @ 0xcae3790b 'Unknown (Type 135)' PASSED: Test 2, Entry @ 0xcae3791f 'Unknown (Type 140)' PASSED: Test 2, Entry @ 0xcae37943 'Unknown (Type 135)' PASSED: Test 2, Entry @ 0xcae3794f 'Hardware Security (Type 24)' PASSED: Test 2, Entry @ 0xcae37956 'Unknown (Type 132)' PASSED: Test 2, Entry @ 0xcae3795f 'Unknown (Type 135)' PASSED: Test 2, Entry @ 0xcae37973 'End of Table (Type 127)' ================================================================================ 57 passed, 18 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ microcode: Test if system is using latest microcode. -------------------------------------------------------------------------------- Test 1 of 1: Test for most recent microcode being loaded. This test verifies if the firmware has put a recent revision 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. SKIPPED: Test 1, Could not determine from kernel log if latest microcode has been loaded. ================================================================================ 0 passed, 0 failed, 0 warning, 0 aborted, 1 skipped, 0 info only. ================================================================================ msr: MSR register tests. -------------------------------------------------------------------------------- Test 1 of 5: Test CPU generic MSRs. PASSED: Test 1, MSR 0x00000001 P5_MC_TYPE is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000006 MONITOR_FILTER_SIZE is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000017 PLATFORM_ID is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000002a EBL_CR_POWERON is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000001b APIC_BASE is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000003a FEATURE_CONTROL is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000008b BIOS_SIGN_ID is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000000fe MTRRCAP is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000174 SYSENTER_CS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000175 SYSENTER_ESP is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000176 SYSENTER_EIP is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000179 MCG_CAP is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000017a MCG_STATUS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000019a CLOCK_MODULATION is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000019b THERM_INTERRUPT is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000001a0 MISC_ENABLE is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000001b2 PACKAGE_THERM_INTERRUPT is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000001f2 SMRR_PHYSBASE is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000001f3 SMRR_PHYSMASK is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000200 MTRR_PHYSBASE0 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000201 MTRR_PHYSMASK0 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000202 MTRR_PHYSBASE1 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000203 MTRR_PHYSMASK1 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000204 MTRR_PHYSBASE2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000205 MTRR_PHYSMASK2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000206 MTRR_PHYSBASE3 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000207 MTRR_PHYSMASK3 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000208 MTRR_PHYSBASE4 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000209 MTRR_PHYSMASK4 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000020a MTRR_PHYSBASE5 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000020b MTRR_PHYSMASK5 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000020c MTRR_PHYSBASE6 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000020d MTRR_PHYSMASK6 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000020e MTRR_PHYSBASE7 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000020f MTRR_PHYSMASK7 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000210 MTRR_PHYSBASE8 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000211 MTRR_PHYSMASK8 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000212 MTRR_PHYSBASE9 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000213 MTRR_PHYSMASK9 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000250 MTRR_FIX64K_000 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000258 MTRR_FIX16K_800 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000259 MTRR_FIX16K_a00 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000268 MTRR_FIX4K_C000 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000269 MTRR_FIX4K_C800 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000026a MTRR_FIX4K_D000 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000026b MTRR_FIX4K_D800 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000026c MTRR_FIX4K_E000 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000026d MTRR_FIX4K_E800 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000026e MTRR_FIX4K_F000 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000026f MTRR_FIX4K_F800 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000277 PAT is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000280 MC0_CTL2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000281 MC1_CTL2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000282 MC2_CTL2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000283 MC3_CTL2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000284 MC4_CTL2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000285 MC5_CTL2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000286 MC6_CTL2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000002ff MTRR_DEF_TYPE is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000003f1 PEBS_ENABLE is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000480 VMX_BASIC is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000481 VMX_PINPASED_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000482 VMX_PROCBASED_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000483 VMX_EXIT_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000484 VMX_ENTRY_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000485 VMX_MISC is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000486 VMX_CR0_FIXED0 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000487 VMX_CR0_FIXED1 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000488 VMX_CR4_FIXED0 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000489 VMX_CR4_FIXED1 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000048a VMX_VMX_VMCS_ENUM is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000048b VMX_PROCBASED_CTLS2 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000048c VMX_EPT_VPID_CAP is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000048d VMX_TRUE_PINBASED_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000048e VMX_TRUE_PROCBASED_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x0000048f VMX_TRUE_EXIT_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x00000490 VMX_TRUE_ENTRY_CTLS is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000004c5 A_PMC4 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000004c6 A_PMC5 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000004c7 A_PMC6 is consistent across 2 CPUs. PASSED: Test 1, MSR 0x000004c8 A_PMC7 is consistent across 2 CPUs. PASSED: Test 1, MSR 0xc0000080 EFER is consistent across 2 CPUs. PASSED: Test 1, MSR 0xc0000081 STAR is consistent across 2 CPUs. PASSED: Test 1, MSR 0xc0000082 LSTAR is consistent across 2 CPUs. PASSED: Test 1, MSR 0xc0000084 FMASK is consistent across 2 CPUs. PASSED: Test 1, MSR 0xc0000102 KERNEL_GS_BASE is consistent across 2 CPUs. Test 2 of 5: Test CPU specific model MSRs. CPU family: 0x6, model: 0x3a (Ivybridge) PASSED: Test 2, MSR 0x000000ce MSR_PLATFORM_INFO is consistent across 2 CPUs. PASSED: Test 2, MSR 0x000000e2 MSR_PKG_CST_CONFIG_CONTROL is consistent across 2 CPUs. PASSED: Test 2, MSR 0x00000648 MSR_CONFIG_TDP_NOMINAL is consistent across 2 CPUs. PASSED: Test 2, MSR 0x00000649 MSR_CONFIG_TDP_LEVEL1 is consistent across 2 CPUs. PASSED: Test 2, MSR 0x0000064a MSR_CONFIG_TDP_LEVEL2 is consistent across 2 CPUs. PASSED: Test 2, MSR 0x0000064b MSR_CONFIG_TDP_CONTROL is consistent across 2 CPUs. PASSED: Test 2, MSR 0x0000064c MSR_TURBO_ACTIVATION_RATIO is consistent across 2 CPUs. Test 3 of 5: Test all P State Ratios. PASSED: Test 3, MSR 0x000000ce Minimum P-State is consistent across 2 CPUs. PASSED: Test 3, MSR 0x000000ce Maximum P-State is consistent across 2 CPUs. Test 4 of 5: Test C1 and C3 autodemotion. PASSED: Test 4, MSR 0x000000e2 C1 and C3 Autodemotion is consistent across 2 CPUs. C1 and C3 Autodemotion enabled. Test 5 of 5: Test SMRR MSR registers. PASSED: Test 5, MSR 0x000001f2 SMRR_PHYSBASE is consistent across 2 CPUs. PASSED: Test 5, MSR 0x000001f2 SMRR_TYPE is consistent across 2 CPUs. PASSED: Test 5, MSR 0x000001f3 SMRR_PHYSMASK is consistent across 2 CPUs. PASSED: Test 5, MSR 0x000001f3 SMRR_VALID is consistent across 2 CPUs. ================================================================================ 100 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ nx: Test if CPU NX is disabled by the BIOS. -------------------------------------------------------------------------------- Test 1 of 3: Test CPU NX capability. PASSED: Test 1, CPU has NX flags, BIOS is not disabling it. Test 2 of 3: Test all CPUs have same BIOS set NX flag. This test verifies that all CPUs have the same NX flag setting. Although rare, BIOS may set the NX flag differently per CPU. PASSED: Test 2, All 2 CPUs have the same NX flag set. Test 3 of 3: Test all CPUs have same msr setting in MSR 0x1a0. This test verifies that all CPUs have the same NX flag setting by examining the per CPU MSR register 0x1a0. PASSED: Test 3, All 2 CPUs have the NX flag in MSR 0x1a0 set. ================================================================================ 3 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ cpufreq: CPU frequency scaling tests. -------------------------------------------------------------------------------- Test 1 of 1: CPU P-State tests. 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. BIOS doing Sw_All P-state coordination across cores. 5. BIOS doing Sw_Any P-state coordination across cores. Results generated by fwts: Version V14.01.01 (2014-01-24 03:21:43). Some of this work - Copyright (c) 1999 - 2014, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2014, Canonical. This test run on 25/02/14 at 05:25:06 on host Linux 201307-13944 3.11.0-17-generic #31~precise1-Ubuntu SMP Tue Feb 4 21:25:43 UTC 2014 x86_64. Command: "fwts -q --stdout-summary -r hibernate-single --s4-device-check --s4-device-check-delay 45 --s4-sleep-delay 120 s4". Running tests: s4. s4: S4 hibernate/resume test. -------------------------------------------------------------------------------- Test 1 of 1: S4 hibernate/resume test. Defaulted to run 1 test, run --s4-multiple=N to run more S4 cycles S4 cycle 1 of 1 Network Controller configurations differ, before: PCI: 0000:03:00.0, VID: e4:27, Class: 02:80 (Network controller) Config: 0000: e4 14 27 47 06 00 18 00 01 00 80 02 10 00 00 00 ..'G............ 0010: 04 00 50 f3 00 00 00 00 00 00 00 00 00 00 00 00 ..P............. 0020: 00 00 00 00 00 00 00 00 00 00 00 00 e4 14 08 06 ................ 0030: 00 00 00 00 40 00 00 00 00 00 00 00 07 01 00 00 ....@........... PCI: 0000:04:00.0, VID: ec:68, Class: 02:00 (Ethernet controller) Config: 0000: ec 10 68 81 07 04 10 00 07 00 00 02 10 00 00 00 ..h............. 0010: 01 20 00 00 00 00 00 00 0c 40 40 f3 00 00 00 00 . .......@@..... 0020: 0c 00 40 f3 00 00 00 00 00 00 00 00 aa 17 13 50 ..@............P 0030: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00 ....@........... versus after: PCI: 0000:03:00.0, VID: e4:27, Class: 02:80 (Network controller) Config: 0000: e4 14 27 47 06 00 10 00 01 00 80 02 10 00 00 00 ..'G............ 0010: 04 00 50 f3 00 00 00 00 00 00 00 00 00 00 00 00 ..P............. 0020: 00 00 00 00 00 00 00 00 00 00 00 00 e4 14 08 06 ................ 0030: 00 00 00 00 40 00 00 00 00 00 00 00 07 01 00 00 ....@........... PCI: 0000:04:00.0, VID: ec:68, Class: 02:00 (Ethernet controller) Config: 0000: ec 10 68 81 07 04 10 00 07 00 00 02 10 00 00 00 ..h............. 0010: 01 20 00 00 00 00 00 00 0c 40 40 f3 00 00 00 00 . .......@@..... 0020: 0c 00 40 f3 00 00 00 00 00 00 00 00 aa 17 13 50 ..@............P 0030: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00 ....@........... FAILED [HIGH] DevConfigDiffAfterS4: Test 1, Found 1 differences in device configuation during S4 cycle. PASSED: Test 1, No kernel log errors detected. PASSED: Test 1, No PM related hibernate issues detected. Found 1 device errors. PASSED: Test 1, No kernel oopses detected. PASSED: Test 1, No kernel WARN_ON warnings detected. Found 1 errors and 0 oopses doing 1 hibernate/resume cycle(s). ================================================================================ 4 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ 4 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. Test Failure Summary ================================================================================ Critical failures: NONE High failures: 1 s4: Found 1 differences in device configuation during S4 cycle. Medium failures: NONE Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---------------+-----+-----+-----+-----+-----+-----+ s4 | 4| 1| | | | | ---------------+-----+-----+-----+-----+-----+-----+ Total: | 4| 1| 0| 0| 0| 0| ---------------+-----+-----+-----+-----+-----+-----+