API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Oct 28th, 2011
121
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.74 KB | None | 0 0
raw download clone embed print report
  1. -------------------------------------------------
  2. Date: Fri Oct 28 22:02:32 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 athlon i386 GNU/Linux
  15.  
  16.  
  17. SUMMARY: 3 Fails, 5 Warns, 12 Pass, 20 Total
  18.  
  19. =================================================
  20. * Plugin name: pciresource
  21. * Result: FAIL
  22.  
  23. * Title: Validate assigned PCI resources
  24. * 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.
  25. ================================================
  26.  
  27. [FAIL]-Device 0000:00:00.0 has incorrect resources
  28.  
  29. PCI: Cannot allocate resource region 3 of device 0000:00:00.0
  30.  
  31. [FAIL]-HPET resources incorrect
  32.  
  33. hpet_resources: 0xfed00000 is busy
  34.  
  35. =================================================
  36. * Plugin name: edd
  37. * Result: FAIL
  38.  
  39. * Title: EDD Boot disk hinting
  40. * 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.
  41. ================================================
  42.  
  43. [FAIL]-Boot device 0x80 does not support EDD
  44.  
  45.  
  46. =================================================
  47. * Plugin name: cpufreq
  48. * Result: FAIL
  49.  
  50. * Title: CPU frequency scaling tests (1-2 mins)
  51. * 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:
  52. 1) Each processor has the same number of frequency states
  53. 2) Higher advertised frequencies have a higher performance
  54. 3) No duplicate frequency values are reported by the BIOS
  55. 4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  56. 5) Is BIOS wrongly doing Sw_Any P-state coordination across cores
  57.  
  58. ================================================
  59.  
  60. [INFO]-4 CPU frequency steps supported
  61.  
  62. Frequency | Speed
  63. -----------+---------
  64. 3.05 Ghz | 100.0 %
  65. 2.35 Ghz | 77.9 %
  66. 1.85 Ghz | 61.7 %
  67. 800 Mhz | 28.1 %
  68.  
  69.  
  70. [FAIL]-Processors are set to SW_ANY
  71.  
  72. [FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ANY instead?
  73.  
  74.  
  75. =================================================
  76. * Plugin name: acpicompile
  77. * Result: WARN
  78.  
  79. * Title: DSDT AML verification
  80. * 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.
  81. ================================================
  82.  
  83. [WARN]-Not all control paths return a value (WMAA)
  84.  
  85. Not all control paths return a value (WMAA)
  86. At line #2189 of DSDT.dsl:
  87.  
  88. | /* 0008 */ 0x00, 0xA0, 0xC9, 0x06, 0x29, 0x10, 0x00, 0x00,
  89. | /* 0010 */ 0x41, 0x41, 0x01, 0x02, 0x21, 0x12, 0x90, 0x05,
  90. | /* 0018 */ 0x66, 0xD5, 0xD1, 0x11, 0xB2, 0xF0, 0x00, 0xA0,
  91. | /* 0020 */ 0xC9, 0x06, 0x29, 0x10, 0x42, 0x41, 0x01, 0x00
  92. | })
  93. >>> Method (WMAA, 3, NotSerialized)
  94. | {
  95. | If (LEqual (Arg0, 0x00))
  96. | {
  97. | If (LOr (LOr (LNotEqual (Arg1, 0x01), LNotEqual (Arg1,
  98.  
  99.  
  100. [WARN]-Reserved method must return a value (_WAK)
  101.  
  102. Reserved method must return a value (_WAK)
  103. At line #2358 of DSDT.dsl:
  104.  
  105. | If (LEqual (Arg0, 0x01)) {}
  106. | If (LEqual (Arg0, 0x05)) {}
  107. | SPTS (Arg0)
  108. | }
  109. |
  110. >>> Method (\_WAK, 1, NotSerialized)
  111. | {
  112. | Store (0xFF, DBG1)
  113. | If (LEqual (Arg0, 0x04))
  114. | {
  115.  
  116.  
  117. [PASS]-Tested table DSDT.dsl
  118.  
  119. [PASS]-Tested table SSDT.dsl
  120.  
  121. [INFO]-The IASL compiler from Intel would save 1739 bytes of space.
  122.  
  123. The existing code takes 26493 bytes
  124. The IASL compiler from Intel uses 24754 bytes
  125. This is a saving of 1739 bytes.
  126.  
  127.  
  128. =================================================
  129. * Plugin name: maxreadreq
  130. * Result: WARN
  131.  
  132. * Title: PCI Express MaxReadReq tuning
  133. * Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
  134. ================================================
  135.  
  136. [WARN]-MaxReadReq for device pci://00:01:00.0 is low (128)
  137.  
  138. [WARN]-MaxReadReq for device pci://00:01:00.1 is low (128)
  139.  
  140. =================================================
  141. * Plugin name: thermal_trip
  142. * Result: WARN
  143.  
  144. * Title: ACPI passive thermal trip points
  145. * Description: This test determines if the passive trip point works as expected.
  146. ================================================
  147.  
  148. [WARN]-No thermal zones found.
  149.  
  150. =================================================
  151. * Plugin name: fan
  152. * Result: WARN
  153.  
  154. * Title: Fan tests
  155. * Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
  156. ================================================
  157.  
  158. [WARN]-No fan information present
  159.  
  160. =================================================
  161. * Plugin name: chk_hpet
  162. * Result: WARN
  163.  
  164. * Title: HPET configuration test
  165. * 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.
  166. ================================================
  167.  
  168. [WARN]-HPET driver in the kernel is enabled, inaccurate results follow.
  169.  
  170. [INFO]-HPET found, VendorID is: 4353
  171.  
  172. =================================================
  173. * Plugin name: battery
  174. * Result: INFO
  175.  
  176. * Title: Battery tests
  177. * 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.
  178.  
  179. 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.
  180. ================================================
  181.  
  182. [INFO]-No battery information present
  183.  
  184. =================================================
  185. * Plugin name: acpiinfo
  186. * Result: INFO
  187.  
  188. * Title: General ACPI information
  189. * 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.
  190. ================================================
  191.  
  192. [INFO]-DSDT was compiled by the Microsoft AML compiler
  193.  
  194. ACPI: DSDT CFEE30C0, 677D (r1 GBT GBTUACPI 1000 MSFT 3000000)
  195.  
  196. =================================================
  197. * Plugin name: DMAR
  198. * Result: INFO
  199.  
  200. * Title: (experimental) DMA Remapping (VT-d) test
  201. * Description: Verify if DMA remapping is sane.
  202. ================================================
  203.  
  204. [INFO]-No DMAR ACPI table found.
  205.  
  206. =================================================
  207. * Plugin name: mtrr
  208. * Result: PASS
  209.  
  210. * Title: MTRR validation
  211. * Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
  212. ================================================
  213.  
  214. =================================================
  215. * Plugin name: SUN
  216. * Result: PASS
  217.  
  218. * Title: SUN duplicate test
  219. * 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.
  220. ================================================
  221.  
  222. [PASS]-Tested _SUN ids, successfully found no duplicates
  223.  
  224. =================================================
  225. * Plugin name: virt
  226. * Result: PASS
  227.  
  228. * Title: SVM Virtualization extensions
  229. * Description: This test checks if SVM is set up correctly
  230. ================================================
  231.  
  232. =================================================
  233. * Plugin name: ebda
  234. * Result: PASS
  235.  
  236. * Title: EBDA region
  237. * Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
  238. ================================================
  239.  
  240. [PASS]-EBDA region is correctly reserved in the E820 table.
  241.  
  242. =================================================
  243. * Plugin name: os2gap
  244. * Result: PASS
  245.  
  246. * Title: OS/2 memory hole test
  247. * Description: This test checks if the OS/2 15Mb memory hole is absent
  248. ================================================
  249.  
  250. [PASS]-Successfully found no 15mb memory hole
  251.  
  252. =================================================
  253. * Plugin name: dmi
  254. * Result: PASS
  255.  
  256. * Title: DMI information check
  257. * Description: This test checks the DMI/SMBIOS tables for common errors.
  258. ================================================
  259.  
  260. [PASS]-Successfully found no errors in SMBIOS/DMI
  261.  
  262. =================================================
  263. * Plugin name: ethernet
  264. * Result: PASS
  265.  
  266. * Title: Ethernet functionality
  267. * 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.
  268.  
  269. 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.
  270. ================================================
  271.  
  272. =================================================
  273. * Plugin name: apicedge
  274. * Result: PASS
  275.  
  276. * Title: (experimental) APIC Edge/Level check
  277. * Description: This test checks if legacy interrupts are edge and PCI interrupts are level
  278. ================================================
  279.  
  280. =================================================
  281. * Plugin name: microcode
  282. * Result: PASS
  283.  
  284. * Title: Processor microcode update
  285. * 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.
  286. ================================================
  287.  
  288.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!