Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Oct 20th, 2011  |  syntax: None  |  size: 16.91 KB  |  views: 76  |  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 17:37:31 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]-Unknown reserved name (_S5D)
  28.  
  29. Unknown reserved name (_S5D)
  30. At line #458 of DSDT.dsl:
  31.  
  32.  |              Method (_S4D, 0, NotSerialized)
  33.  |              {
  34.  |                  Return (0x03)
  35.  |              }
  36.  |  
  37. >>>             Method (_S5D, 0, NotSerialized)
  38.  |              {
  39.  |                  Return (0x03)
  40.  |              }
  41.  |          }
  42.  
  43.  
  44. [WARN]-Unknown reserved name (_S5D)
  45.  
  46. Unknown reserved name (_S5D)
  47. At line #485 of DSDT.dsl:
  48.  
  49.  |              Method (_S4D, 0, NotSerialized)
  50.  |              {
  51.  |                  Return (0x03)
  52.  |              }
  53.  |  
  54. >>>             Method (_S5D, 0, NotSerialized)
  55.  |              {
  56.  |                  Return (0x03)
  57.  |              }
  58.  |          }
  59.  
  60.  
  61. [WARN]-Unknown reserved name (_S5D)
  62.  
  63. Unknown reserved name (_S5D)
  64. At line #528 of DSDT.dsl:
  65.  
  66.  |              Method (_S4D, 0, NotSerialized)
  67.  |              {
  68.  |                  Return (0x03)
  69.  |              }
  70.  |  
  71. >>>             Method (_S5D, 0, NotSerialized)
  72.  |              {
  73.  |                  Return (0x03)
  74.  |              }
  75.  |          }
  76.  
  77.  
  78. [WARN]-Unknown reserved name (_S5D)
  79.  
  80. Unknown reserved name (_S5D)
  81. At line #547 of DSDT.dsl:
  82.  
  83.  |              Method (_S4D, 0, NotSerialized)
  84.  |              {
  85.  |                  Return (0x03)
  86.  |              }
  87.  |  
  88. >>>             Method (_S5D, 0, NotSerialized)
  89.  |              {
  90.  |                  Return (0x03)
  91.  |              }
  92.  |          }
  93.  
  94.  
  95. [WARN]-Unknown reserved name (_S5D)
  96.  
  97. Unknown reserved name (_S5D)
  98. At line #566 of DSDT.dsl:
  99.  
  100.  |              Method (_S4D, 0, NotSerialized)
  101.  |              {
  102.  |                  Return (0x03)
  103.  |              }
  104.  |  
  105. >>>             Method (_S5D, 0, NotSerialized)
  106.  |              {
  107.  |                  Return (0x03)
  108.  |              }
  109.  |          }
  110.  
  111.  
  112. [WARN]-Unknown reserved name (_S5D)
  113.  
  114. Unknown reserved name (_S5D)
  115. At line #585 of DSDT.dsl:
  116.  
  117.  |              Method (_S4D, 0, NotSerialized)
  118.  |              {
  119.  |                  Return (0x03)
  120.  |              }
  121.  |  
  122. >>>             Method (_S5D, 0, NotSerialized)
  123.  |              {
  124.  |                  Return (0x03)
  125.  |              }
  126.  |          }
  127.  
  128.  
  129. [PASS]-Tested table DSDT.dsl
  130.  
  131. [PASS]-Tested table SSDT1.dsl
  132.  
  133. [FAIL]-syntax error, unexpected PARSEOP_STORE, expecting ')'
  134.  
  135. syntax error, unexpected PARSEOP_STORE, expecting ')'
  136. At line #79 of SSDT2.dsl:
  137.  
  138.  |  {
  139.  |      CreateDWordField (CRES, 0x0A, T1MG)
  140.  |      CreateDWordField (CRES, 0x0E, PMAX)
  141.  |      CreateDWordField (CRES, 0x16, PCIR)
  142.  |      Add (MLEN (0x00200000, T1MG, Subtract (NPCI, One, PMAX)), Subtract (NPCI,
  143. >>>         T1MG, PCIR), Store (0x6C, Local0))
  144.  |      Store (0x00, Local1)
  145.  |      Store (\GDBF (DCHM, Local1), Local2)
  146.  |      While (LAnd (Local2, LLess (Local1, 0x20)))
  147.  |      {
  148.  
  149.  
  150. [FAIL]-Method local variable is not initialized (Local0)
  151.  
  152. Method local variable is not initialized (Local0)
  153. At line #84 of SSDT2.dsl:
  154.  
  155.  |      T1MG, PCIR), Store (0x6C, Local0))
  156.  |  Store (0x00, Local1)
  157.  |  Store (\GDBF (DCHM, Local1), Local2)
  158.  |  While (LAnd (Local2, LLess (Local1, 0x20)))
  159.  |  {
  160. >>>     \SDBF (CRES, Local0, 0x1787)
  161.  |      Add (Local0, 0x0A, Local0)
  162.  |      \SDBF (CRES, Local0, Local2)
  163.  |      Add (Local0, 0x04, Local0)
  164.  |      Add (Local1, 0x04, Local1)
  165.  
  166.  
  167. [FAIL]-Method local variable is not initialized (Local0)
  168.  
  169. Method local variable is not initialized (Local0)
  170. At line #85 of SSDT2.dsl:
  171.  
  172.  |  Store (0x00, Local1)
  173.  |  Store (\GDBF (DCHM, Local1), Local2)
  174.  |  While (LAnd (Local2, LLess (Local1, 0x20)))
  175.  |  {
  176.  |      \SDBF (CRES, Local0, 0x1787)
  177. >>>     Add (Local0, 0x0A, Local0)
  178.  |      \SDBF (CRES, Local0, Local2)
  179.  |      Add (Local0, 0x04, Local0)
  180.  |      Add (Local1, 0x04, Local1)
  181.  |      Store (\GDBF (DCHM, Local1), Local3)
  182.  
  183.  
  184. [FAIL]-syntax error, unexpected PARSEOP_CREATEDWORDFIELD, expecting ',' or ')'
  185.  
  186. syntax error, unexpected PARSEOP_CREATEDWORDFIELD, expecting ',' or ')'
  187. At line #266 of SSDT2.dsl:
  188.  
  189.  |      /* 0068 */    0x00, 0x00, 0x00, 0x00, 0x79, 0x00
  190.  |  })
  191.  |  Method (_CRS, 0, NotSerialized)
  192.  |  {
  193.  |      CreateDWordField (CRES, 0x14, RAMT)
  194. >>>     Store (MLEN (RAMT, CreateDWordField (CRES, 0x1C, RMT2), Add (MLEN (0x00100000,
  195.  |          RMT2, CreateDWordField (CRES, 0x28, CE0S)), Store (E00S, CE0S), CreateDWordField (CRES, 0x2C,
  196.  |          CE0L))), Store (0x00100000, Local0))
  197.  |      Subtract (Local0, E00S, CE0L)
  198.  |      CreateDWordField (CRES, 0x34, S4GS)
  199.  
  200.  
  201. [FAIL]-syntax error, unexpected PARSEOP_CREATEDWORDFIELD, expecting ',' or ')'
  202.  
  203. syntax error, unexpected PARSEOP_CREATEDWORDFIELD, expecting ',' or ')'
  204. At line #267 of SSDT2.dsl:
  205.  
  206.  |  })
  207.  |  Method (_CRS, 0, NotSerialized)
  208.  |  {
  209.  |      CreateDWordField (CRES, 0x14, RAMT)
  210.  |      Store (MLEN (RAMT, CreateDWordField (CRES, 0x1C, RMT2), Add (MLEN (0x00100000,
  211. >>>         RMT2, CreateDWordField (CRES, 0x28, CE0S)), Store (E00S, CE0S), CreateDWordField (CRES, 0x2C,
  212.  |          CE0L))), Store (0x00100000, Local0))
  213.  |      Subtract (Local0, E00S, CE0L)
  214.  |      CreateDWordField (CRES, 0x34, S4GS)
  215.  |      Store (SR4G, S4GS)
  216.  
  217.  
  218. [FAIL]-syntax error, unexpected ','
  219.  
  220. syntax error, unexpected ','
  221. At line #267 of SSDT2.dsl:
  222.  
  223.  |  })
  224.  |  Method (_CRS, 0, NotSerialized)
  225.  |  {
  226.  |      CreateDWordField (CRES, 0x14, RAMT)
  227.  |      Store (MLEN (RAMT, CreateDWordField (CRES, 0x1C, RMT2), Add (MLEN (0x00100000,
  228. >>>         RMT2, CreateDWordField (CRES, 0x28, CE0S)), Store (E00S, CE0S), CreateDWordField (CRES, 0x2C,
  229.  |          CE0L))), Store (0x00100000, Local0))
  230.  |      Subtract (Local0, E00S, CE0L)
  231.  |      CreateDWordField (CRES, 0x34, S4GS)
  232.  |      Store (SR4G, S4GS)
  233.  
  234.  
  235. [FAIL]-syntax error, unexpected ')'
  236.  
  237. syntax error, unexpected ')'
  238. At line #268 of SSDT2.dsl:
  239.  
  240.  |  Method (_CRS, 0, NotSerialized)
  241.  |  {
  242.  |      CreateDWordField (CRES, 0x14, RAMT)
  243.  |      Store (MLEN (RAMT, CreateDWordField (CRES, 0x1C, RMT2), Add (MLEN (0x00100000,
  244.  |          RMT2, CreateDWordField (CRES, 0x28, CE0S)), Store (E00S, CE0S), CreateDWordField (CRES, 0x2C,
  245. >>>         CE0L))), Store (0x00100000, Local0))
  246.  |      Subtract (Local0, E00S, CE0L)
  247.  |      CreateDWordField (CRES, 0x34, S4GS)
  248.  |      Store (SR4G, S4GS)
  249.  |      CreateDWordField (CRES, 0x38, S4GL)
  250.  
  251.  
  252. [FAIL]-syntax error, unexpected ')'
  253.  
  254. syntax error, unexpected ')'
  255. At line #268 of SSDT2.dsl:
  256.  
  257.  |  Method (_CRS, 0, NotSerialized)
  258.  |  {
  259.  |      CreateDWordField (CRES, 0x14, RAMT)
  260.  |      Store (MLEN (RAMT, CreateDWordField (CRES, 0x1C, RMT2), Add (MLEN (0x00100000,
  261.  |          RMT2, CreateDWordField (CRES, 0x28, CE0S)), Store (E00S, CE0S), CreateDWordField (CRES, 0x2C,
  262. >>>         CE0L))), Store (0x00100000, Local0))
  263.  |      Subtract (Local0, E00S, CE0L)
  264.  |      CreateDWordField (CRES, 0x34, S4GS)
  265.  |      Store (SR4G, S4GS)
  266.  |      CreateDWordField (CRES, 0x38, S4GL)
  267.  
  268.  
  269. [FAIL]-syntax error, unexpected PARSEOP_FIELD
  270.  
  271. syntax error, unexpected PARSEOP_FIELD
  272. At line #276 of SSDT2.dsl:
  273.  
  274.  |  Store (SR4G, S4GS)
  275.  |  CreateDWordField (CRES, 0x38, S4GL)
  276.  |  Store (0xFFFFFFFF, Local0)
  277.  |  Subtract (Local0, SR4G, Local0)
  278.  |  Add (Local0, One, S4GL)
  279. >>> OperationRegion (ODMT, SystemMemory, ODDM (0x38), Field (ODMT, DWordAcc, NoLock, Preserve)
  280.  |      {
  281.  |          OMTF,   448
  282.  |      })
  283.  |  Store (0x3C, Local0)
  284.  
  285.  
  286. [PASS]-Tested table SSDT2.dsl
  287.  
  288. [PASS]-Tested table SSDT3.dsl
  289.  
  290. [PASS]-Tested table SSDT4.dsl
  291.  
  292. [PASS]-Tested table SSDT5.dsl
  293.  
  294. [PASS]-Tested table SSDT6.dsl
  295.  
  296. [PASS]-Tested table SSDT7.dsl
  297.  
  298. [PASS]-Tested table SSDT8.dsl
  299.  
  300. [PASS]-Tested table SSDT9.dsl
  301.  
  302. [INFO]-The IASL compiler from Intel would save 179 bytes of space.
  303.  
  304. The existing code takes 2931 bytes
  305. The IASL compiler from Intel uses 2752 bytes
  306. This is a saving of 179 bytes.
  307.  
  308.  
  309. =================================================
  310. * Plugin name: edd
  311. * Result: FAIL
  312.  
  313. * Title: EDD Boot disk hinting
  314. * 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.
  315. ================================================
  316.  
  317. [FAIL]-Boot device 0x80 does not support EDD
  318.  
  319.  
  320. =================================================
  321. * Plugin name: chk_hpet
  322. * Result: FAIL
  323.  
  324. * Title: HPET configuration test
  325. * 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.
  326. ================================================
  327.  
  328. [WARN]-HPET driver in the kernel is enabled, inaccurate results follow.
  329.  
  330. [FAIL]-Failed to locate HPET base
  331.  
  332. The firmware AML code doesn't advertize the HPET base.
  333. HPET might be disabled in the bios settings, or not supported by the platform.
  334.  
  335. =================================================
  336. * Plugin name: ethernet
  337. * Result: FAIL
  338.  
  339. * Title: Ethernet functionality
  340. * 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.
  341.  
  342. 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.
  343. ================================================
  344.  
  345. [FAIL]-Failed to acquire link within 45 seconds
  346.  
  347. =================================================
  348. * Plugin name: microcode
  349. * Result: FAIL
  350.  
  351. * Title: Processor microcode update
  352. * 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.
  353. ================================================
  354.  
  355. [FAIL]-Cpu cpu0 has outdated microcode (version b while version 1e is available)
  356.  
  357. =================================================
  358. * Plugin name: thermal_trip
  359. * Result: WARN
  360.  
  361. * Title: ACPI passive thermal trip points
  362. * Description: This test determines if the passive trip point works as expected.
  363. ================================================
  364.  
  365. [WARN]-No thermal zones found.
  366.  
  367. =================================================
  368. * Plugin name: fan
  369. * Result: WARN
  370.  
  371. * Title: Fan tests
  372. * Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
  373. ================================================
  374.  
  375. [WARN]-No fan information present
  376.  
  377. =================================================
  378. * Plugin name: cpufreq
  379. * Result: WARN
  380.  
  381. * Title: CPU frequency scaling tests (1-2 mins)
  382. * 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:
  383.   1) Each processor has the same number of frequency states
  384.   2) Higher advertised frequencies have a higher performance
  385.   3) No duplicate frequency values are reported by the BIOS
  386.   4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  387.   5) Is BIOS wrongly doing Sw_Any P-state coordination across cores
  388.  
  389. ================================================
  390.  
  391. [WARN]-Frequency scaling not supported
  392.  
  393. =================================================
  394. * Plugin name: battery
  395. * Result: INFO
  396.  
  397. * Title: Battery tests
  398. * 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.
  399.  
  400. 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.
  401. ================================================
  402.  
  403. [INFO]-No battery information present
  404.  
  405. =================================================
  406. * Plugin name: acpiinfo
  407. * Result: INFO
  408.  
  409. * Title: General ACPI information
  410. * 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.
  411. ================================================
  412.  
  413. [INFO]-DSDT was compiled by the Microsoft AML compiler
  414.  
  415. ACPI: DSDT 000E68D4, 0B73 (r1 COMPAQ     DSDT        1 MSFT  100000E)
  416.  
  417. =================================================
  418. * Plugin name: virt
  419. * Result: INFO
  420.  
  421. * Title: VT/VMX Virtualization extensions
  422. * Description: This test checks if VT/VMX is set up correctly
  423. ================================================
  424.  
  425. [INFO]-Processor does not support Virtualization extensions
  426.  
  427. =================================================
  428. * Plugin name: DMAR
  429. * Result: INFO
  430.  
  431. * Title: (experimental) DMA Remapping (VT-d) test
  432. * Description: Verify if DMA remapping is sane.
  433. ================================================
  434.  
  435. [INFO]-No DMAR ACPI table found.
  436.  
  437. =================================================
  438. * Plugin name: mtrr
  439. * Result: PASS
  440.  
  441. * Title: MTRR validation
  442. * Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
  443. ================================================
  444.  
  445. =================================================
  446. * Plugin name: pciresource
  447. * Result: PASS
  448.  
  449. * Title: Validate assigned PCI resources
  450. * 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.
  451. ================================================
  452.  
  453. =================================================
  454. * Plugin name: maxreadreq
  455. * Result: PASS
  456.  
  457. * Title: PCI Express MaxReadReq tuning
  458. * Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
  459. ================================================
  460.  
  461. =================================================
  462. * Plugin name: SUN
  463. * Result: PASS
  464.  
  465. * Title: SUN duplicate test
  466. * 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.
  467. ================================================
  468.  
  469. [PASS]-Tested _SUN ids, successfully found no duplicates
  470.  
  471. =================================================
  472. * Plugin name: ebda
  473. * Result: PASS
  474.  
  475. * Title: EBDA region
  476. * Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
  477. ================================================
  478.  
  479. [PASS]-EBDA region is correctly reserved in the E820 table.
  480.  
  481. =================================================
  482. * Plugin name: os2gap
  483. * Result: PASS
  484.  
  485. * Title: OS/2 memory hole test
  486. * Description: This test checks if the OS/2 15Mb memory hole is absent
  487. ================================================
  488.  
  489. [PASS]-Successfully found no 15mb memory hole
  490.  
  491. =================================================
  492. * Plugin name: dmi
  493. * Result: PASS
  494.  
  495. * Title: DMI information check
  496. * Description: This test checks the DMI/SMBIOS tables for common errors.
  497. ================================================
  498.  
  499. [PASS]-Successfully found no errors in SMBIOS/DMI
  500.  
  501. =================================================
  502. * Plugin name: apicedge
  503. * Result: PASS
  504.  
  505. * Title: (experimental) APIC Edge/Level check
  506. * Description: This test checks if legacy interrupts are edge and PCI interrupts are level
  507. ================================================
  508.  
  509.  
  510.  
clone this paste RAW Paste Data