Pastebin is 300% more awesome when you are logged in. Sign Up, it's FREE!
Guest

Advanced Digital Logic ADLGS45PC ACPI test results

By: a guest on Oct 20th, 2011  |  syntax: None  |  size: 10.87 KB  |  hits: 32  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. -------------------------------------------------
  2.   Date: Thu Oct 20 15:59:20 2011                                      
  3. *                                               *
  4. * Firmwarekit (release 3)                       *
  5. * http://www.linuxfirmwarekit.org               *
  6. *                                               *
  7. *                                               *
  8. * For more information on test descriptions     *
  9. * and details on what the PASS/INFO/WARN/FAIL   *
  10. * results mean, go to: Documentation/TestsInfo. *
  11. *                                               *
  12. -------------------------------------------------
  13.  
  14. KERNEL VERSION: Linux testmachine 2.6.22.9 #1 SMP Mon Oct 1 15:17:15 PDT 2007 i686 i686 i386 GNU/Linux
  15.  
  16.  
  17. SUMMARY:  5 Fails, 3 Warns, 12 Pass, 20 Total
  18.  
  19. =================================================
  20. * Plugin name: acpicompile
  21. * Result: FAIL
  22.  
  23. * Title: DSDT AML verification
  24. * 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.
  25. ================================================
  26.  
  27. [WARN]-Reserved method must return a value (_WAK)
  28.  
  29. Reserved method must return a value (_WAK)
  30. At line #531 of DSDT.dsl:
  31.  
  32.  |                  Sleep (0x64)
  33.  |              }
  34.  |          }
  35.  |      }
  36.  |  
  37. >>>     Method (\_WAK, 1, NotSerialized)
  38.  |      {
  39.  |          Store (0xFF, DBG1)
  40.  |          If (LEqual (Arg0, 0x03))
  41.  |          {
  42.  
  43.  
  44. [FAIL]-Method local variable is not initialized (Local0)
  45.  
  46. Method local variable is not initialized (Local0)
  47. At line #566 of DSDT.dsl:
  48.  
  49.  |  
  50.  |      Scope (\_SI)
  51.  |      {
  52.  |          Method (_MSG, 1, NotSerialized)
  53.  |          {
  54. >>>             Store (Local0, Local0)
  55.  |          }
  56.  |  
  57.  |          Method (_SST, 1, NotSerialized)
  58.  |          {
  59.  
  60.  
  61. [FAIL]-Method local variable is not initialized (Local0)
  62.  
  63. Method local variable is not initialized (Local0)
  64. At line #571 of DSDT.dsl:
  65.  
  66.  |              Store (Local0, Local0)
  67.  |          }
  68.  |  
  69.  |          Method (_SST, 1, NotSerialized)
  70.  |          {
  71. >>>             Store (Local0, Local0)
  72.  |          }
  73.  |      }
  74.  |  
  75.  |      Scope (\_GPE)
  76.  
  77.  
  78. [PASS]-Tested table DSDT.dsl
  79.  
  80. [PASS]-Tested table SSDT.dsl
  81.  
  82. =================================================
  83. * Plugin name: pciresource
  84. * Result: FAIL
  85.  
  86. * Title: Validate assigned PCI resources
  87. * 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.
  88. ================================================
  89.  
  90. [FAIL]-HPET resources incorrect
  91.  
  92. hpet_resources: 0xfed00000 is busy
  93.  
  94. =================================================
  95. * Plugin name: thermal_trip
  96. * Result: FAIL
  97.  
  98. * Title: ACPI passive thermal trip points
  99. * Description: This test determines if the passive trip point works as expected.
  100. ================================================
  101.  
  102. [FAIL]-Changing passive trip point seems uneffective in Zone THRM.
  103.  
  104. =================================================
  105. * Plugin name: cpufreq
  106. * Result: FAIL
  107.  
  108. * Title: CPU frequency scaling tests (1-2 mins)
  109. * 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:
  110.   1) Each processor has the same number of frequency states
  111.   2) Higher advertised frequencies have a higher performance
  112.   3) No duplicate frequency values are reported by the BIOS
  113.   4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  114.   5) Is BIOS wrongly doing Sw_Any P-state coordination across cores
  115.  
  116. ================================================
  117.  
  118. [INFO]-2 CPU frequency steps supported
  119.  
  120.  Frequency | Speed
  121. -----------+---------
  122.   1.92 Ghz | 100.0 %
  123.   1.65 Ghz |  85.7 %
  124.  
  125.  
  126. [FAIL]-Processors are set to SW_ANY
  127.  
  128. [FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ALL instead?
  129.  
  130.  
  131. [FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ANY instead?
  132.  
  133.  
  134. =================================================
  135. * Plugin name: dmi
  136. * Result: FAIL
  137.  
  138. * Title: DMI information check
  139. * Description: This test checks the DMI/SMBIOS tables for common errors.
  140. ================================================
  141.  
  142. [FAIL]-No SMBIOS nor DMI entry point found.
  143.  
  144. =================================================
  145. * Plugin name: maxreadreq
  146. * Result: WARN
  147.  
  148. * Title: PCI Express MaxReadReq tuning
  149. * Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
  150. ================================================
  151.  
  152. [WARN]-MaxReadReq for device pci://00:00:1b.0 is low (128)
  153.  
  154. =================================================
  155. * Plugin name: edd
  156. * Result: WARN
  157.  
  158. * Title: EDD Boot disk hinting
  159. * 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.
  160. ================================================
  161.  
  162. [INFO]-device 80: The system boots from device 0000:00:1f.5 channel: 0 device: 0
  163.  
  164.  
  165. [WARN]-device 80: No matching MBR signature (0x000dd21b) found for the boot disk
  166.  
  167. Device sda - signature 0x44fdfe06
  168.  
  169.  
  170. [INFO]-device 81 is provided by device 0000:00:1d.7 channel: 0 serial_number: 30384c5032303231
  171.  
  172.  
  173. [INFO]-device 81: This disk has Linux device name /dev/sda
  174.  
  175. =================================================
  176. * Plugin name: chk_hpet
  177. * Result: WARN
  178.  
  179. * Title: HPET configuration test
  180. * 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.
  181. ================================================
  182.  
  183. [WARN]-HPET driver in the kernel is enabled, inaccurate results follow.
  184.  
  185. [INFO]-HPET found, VendorID is: 8086
  186.  
  187. =================================================
  188. * Plugin name: battery
  189. * Result: INFO
  190.  
  191. * Title: Battery tests
  192. * 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.
  193.  
  194. 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.
  195. ================================================
  196.  
  197. [INFO]-No battery information present
  198.  
  199. =================================================
  200. * Plugin name: acpiinfo
  201. * Result: INFO
  202.  
  203. * Title: General ACPI information
  204. * 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.
  205. ================================================
  206.  
  207. [INFO]-DSDT was compiled by the Microsoft AML compiler
  208.  
  209. ACPI: DSDT 7BCE3200, 72A8 (r1 INTELR AWRDACPI     1000 MSFT  3000000)
  210.  
  211. =================================================
  212. * Plugin name: DMAR
  213. * Result: INFO
  214.  
  215. * Title: (experimental) DMA Remapping (VT-d) test
  216. * Description: Verify if DMA remapping is sane.
  217. ================================================
  218.  
  219. [INFO]-No DMAR ACPI table found.
  220.  
  221. =================================================
  222. * Plugin name: mtrr
  223. * Result: PASS
  224.  
  225. * Title: MTRR validation
  226. * Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
  227. ================================================
  228.  
  229. =================================================
  230. * Plugin name: SUN
  231. * Result: PASS
  232.  
  233. * Title: SUN duplicate test
  234. * 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.
  235. ================================================
  236.  
  237. [PASS]-Tested _SUN ids, successfully found no duplicates
  238.  
  239. =================================================
  240. * Plugin name: fan
  241. * Result: PASS
  242.  
  243. * Title: Fan tests
  244. * Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
  245. ================================================
  246.  
  247. [PASS]-Fan FAN status is: on
  248.  
  249. =================================================
  250. * Plugin name: virt
  251. * Result: PASS
  252.  
  253. * Title: VT/VMX Virtualization extensions
  254. * Description: This test checks if VT/VMX is set up correctly
  255. ================================================
  256.  
  257. =================================================
  258. * Plugin name: ebda
  259. * Result: PASS
  260.  
  261. * Title: EBDA region
  262. * Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
  263. ================================================
  264.  
  265. [PASS]-EBDA region is correctly reserved in the E820 table.
  266.  
  267. =================================================
  268. * Plugin name: os2gap
  269. * Result: PASS
  270.  
  271. * Title: OS/2 memory hole test
  272. * Description: This test checks if the OS/2 15Mb memory hole is absent
  273. ================================================
  274.  
  275. [PASS]-Successfully found no 15mb memory hole
  276.  
  277. =================================================
  278. * Plugin name: ethernet
  279. * Result: PASS
  280.  
  281. * Title: Ethernet functionality
  282. * 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.
  283.  
  284. 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.
  285. ================================================
  286.  
  287. =================================================
  288. * Plugin name: apicedge
  289. * Result: PASS
  290.  
  291. * Title: (experimental) APIC Edge/Level check
  292. * Description: This test checks if legacy interrupts are edge and PCI interrupts are level
  293. ================================================
  294.  
  295. =================================================
  296. * Plugin name: microcode
  297. * Result: PASS
  298.  
  299. * Title: Processor microcode update
  300. * 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.
  301. ================================================
  302.  
  303.