API tools faq
paste
Advertisement
Guest User

F1A75-firmarekit.txt

a guest
Nov 8th, 2011
194
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 24.14 KB | None | 0 0
raw download clone embed print report
  1. -------------------------------------------------
  2. Date: Tue Nov 8 17:16:19 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: 4 Fails, 5 Warns, 11 Pass, 20 Total
  18.  
  19. =================================================
  20. * Plugin name: mtrr
  21. * Result: FAIL
  22.  
  23. * Title: MTRR validation
  24. * Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
  25. ================================================
  26.  
  27. [FAIL]-Memory range 0xc0000000 to 0xcfffffff (0000:00:01.0) has incorrect attribute uncached write-back
  28.  
  29. Memory range 0xc0000000 to 0xcfffffff (0000:00:01.0) has incorrect attribute uncached write-back
  30.  
  31. [FAIL]-Memory range 0xd0000000 to 0xd0003fff (0000:03:00.0) has incorrect attribute uncached write-back
  32.  
  33. Memory range 0xd0000000 to 0xd0003fff (0000:03:00.0) has incorrect attribute uncached write-back
  34.  
  35. [FAIL]-Memory range 0xd0004000 to 0xd0004fff (0000:03:00.0) has incorrect attribute uncached write-back
  36.  
  37. Memory range 0xd0004000 to 0xd0004fff (0000:03:00.0) has incorrect attribute uncached write-back
  38.  
  39. [FAIL]-Memory range 0xfe900000 to 0xfe907fff (0000:04:00.0) has incorrect attribute write-back
  40.  
  41. Memory range 0xfe900000 to 0xfe907fff (0000:04:00.0) has incorrect attribute write-back
  42.  
  43. [FAIL]-Memory range 0xfea00000 to 0xfea0ffff (0000:02:00.0) has incorrect attribute write-back
  44.  
  45. Memory range 0xfea00000 to 0xfea0ffff (0000:02:00.0) has incorrect attribute write-back
  46.  
  47. [FAIL]-Memory range 0xfeb00000 to 0xfeb3ffff (0000:00:01.0) has incorrect attribute write-back
  48.  
  49. Memory range 0xfeb00000 to 0xfeb3ffff (0000:00:01.0) has incorrect attribute write-back
  50.  
  51. [FAIL]-Memory range 0xfeb40000 to 0xfeb43fff (0000:00:14.2) has incorrect attribute write-back
  52.  
  53. Memory range 0xfeb40000 to 0xfeb43fff (0000:00:14.2) has incorrect attribute write-back
  54.  
  55. [FAIL]-Memory range 0xfeb44000 to 0xfeb47fff (0000:00:01.1) has incorrect attribute write-back
  56.  
  57. Memory range 0xfeb44000 to 0xfeb47fff (0000:00:01.1) has incorrect attribute write-back
  58.  
  59. [FAIL]-Memory range 0xfeb48000 to 0xfeb49fff (0000:00:10.1) has incorrect attribute write-back
  60.  
  61. Memory range 0xfeb48000 to 0xfeb49fff (0000:00:10.1) has incorrect attribute write-back
  62.  
  63. [FAIL]-Memory range 0xfeb4a000 to 0xfeb4bfff (0000:00:10.0) has incorrect attribute write-back
  64.  
  65. Memory range 0xfeb4a000 to 0xfeb4bfff (0000:00:10.0) has incorrect attribute write-back
  66.  
  67. [FAIL]-Memory range 0xfeb4c000 to 0xfeb4cfff (0000:00:14.5) has incorrect attribute write-back
  68.  
  69. Memory range 0xfeb4c000 to 0xfeb4cfff (0000:00:14.5) has incorrect attribute write-back
  70.  
  71. [FAIL]-Memory range 0xfeb4d000 to 0xfeb4d0ff (0000:00:13.2) has incorrect attribute write-back
  72.  
  73. Memory range 0xfeb4d000 to 0xfeb4d0ff (0000:00:13.2) has incorrect attribute write-back
  74.  
  75. [FAIL]-Memory range 0xfeb4e000 to 0xfeb4efff (0000:00:13.0) has incorrect attribute write-back
  76.  
  77. Memory range 0xfeb4e000 to 0xfeb4efff (0000:00:13.0) has incorrect attribute write-back
  78.  
  79. [FAIL]-Memory range 0xfeb4f000 to 0xfeb4f0ff (0000:00:12.2) has incorrect attribute write-back
  80.  
  81. Memory range 0xfeb4f000 to 0xfeb4f0ff (0000:00:12.2) has incorrect attribute write-back
  82.  
  83. [FAIL]-Memory range 0xfeb50000 to 0xfeb50fff (0000:00:12.0) has incorrect attribute write-back
  84.  
  85. Memory range 0xfeb50000 to 0xfeb50fff (0000:00:12.0) has incorrect attribute write-back
  86.  
  87. [FAIL]-Memory range 0xfeb51000 to 0xfeb517ff (0000:00:11.0) has incorrect attribute write-back
  88.  
  89. Memory range 0xfeb51000 to 0xfeb517ff (0000:00:11.0) has incorrect attribute write-back
  90.  
  91. =================================================
  92. * Plugin name: acpicompile
  93. * Result: FAIL
  94.  
  95. * Title: DSDT AML verification
  96. * 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.
  97. ================================================
  98.  
  99. [WARN]-Possible operator timeout is ignored
  100.  
  101. Possible operator timeout is ignored
  102. At line #3945 of DSDT.dsl:
  103.  
  104. | 0xFF
  105. | })
  106. | Mutex (MUT0, 0x00)
  107. | Method (ENFG, 1, NotSerialized)
  108. | {
  109. >>> Acquire (MUT0, 0x0FFF)
  110. | Store (0x87, INDX)
  111. | Store (One, INDX)
  112. | Store (0x55, INDX)
  113. | If (LEqual (SP1O, 0x2E))
  114.  
  115.  
  116. [WARN]-Result is not used, operator has no effect
  117.  
  118. Result is not used, operator has no effect
  119. At line #6538 of DSDT.dsl:
  120.  
  121. | CreateDWordField (Arg3, 0x08, CDW3)
  122. | Store (CDW2, SUPP)
  123. | Store (CDW3, CTRL)
  124. | If (LNotEqual (And (SUPP, 0x16), 0x16))
  125. | {
  126. >>> And (CTRL, 0x1E)
  127. | }
  128. |
  129. | If (LNot (PEHP))
  130. | {
  131.  
  132.  
  133. [FAIL]-Use of reserved word (_T_0)
  134.  
  135. Use of reserved word (_T_0)
  136. At line #6819 of DSDT.dsl:
  137.  
  138. | }
  139. |
  140. | Method (WMBC, 3, NotSerialized)
  141. | {
  142. | Store (One, Local0)
  143. >>> Name (_T_0, Zero)
  144. | Store (Arg1, _T_0)
  145. | If (LEqual (_T_0, 0x43455053))
  146. | {
  147. | Return (SPEC (Arg2))
  148.  
  149.  
  150. [FAIL]-Use of reserved word (_T_0)
  151.  
  152. Use of reserved word (_T_0)
  153. At line #6922 of DSDT.dsl:
  154.  
  155. | }
  156. |
  157. | Method (WMBD, 3, NotSerialized)
  158. | {
  159. | Store (One, Local0)
  160. >>> Name (_T_0, Zero)
  161. | Store (Arg1, _T_0)
  162. | If (LEqual (_T_0, 0x424D5352))
  163. | {
  164. | Return (RSMB (Arg2))
  165.  
  166.  
  167. [FAIL]-Use of reserved word (_T_0)
  168.  
  169. Use of reserved word (_T_0)
  170. At line #7327 of DSDT.dsl:
  171.  
  172. | {
  173. | CreateDWordField (Arg0, Zero, DVID)
  174. | CreateDWordField (Arg0, 0x04, PARA)
  175. | If (LEqual (PARA, One))
  176. | {
  177. >>> Name (_T_0, Zero)
  178. | Store (DVID, _T_0)
  179. | If (LEqual (_T_0, 0x00010011))
  180. | {
  181. | Or (\_SB.DSAF, One, \_SB.DSAF)
  182.  
  183.  
  184. [FAIL]-Use of reserved word (_T_1)
  185.  
  186. Use of reserved word (_T_1)
  187. At line #7475 of DSDT.dsl:
  188.  
  189. | }
  190. | Else
  191. | {
  192. | If (LEqual (PARA, Zero))
  193. | {
  194. >>> Name (_T_1, Zero)
  195. | Store (DVID, _T_1)
  196. | If (LEqual (_T_1, 0x00010011))
  197. | {
  198. | And (\_SB.DSAF, 0xFFFFFFFFFFFFFFFE, \_SB.DSAF)
  199.  
  200.  
  201. [FAIL]-Use of reserved word (_T_0)
  202.  
  203. Use of reserved word (_T_0)
  204. At line #7640 of DSDT.dsl:
  205.  
  206. |
  207. | Method (DEVS, 1, Serialized)
  208. | {
  209. | CreateDWordField (Arg0, Zero, DVID)
  210. | CreateDWordField (Arg0, 0x04, CPAR)
  211. >>> Name (_T_0, Zero)
  212. | Store (DVID, _T_0)
  213. | If (LEqual (_T_0, Zero))
  214. | {
  215. | Return (Zero)
  216.  
  217.  
  218. [FAIL]-Use of reserved word (_T_0)
  219.  
  220. Use of reserved word (_T_0)
  221. At line #7655 of DSDT.dsl:
  222.  
  223. | }
  224. |
  225. | Method (DSTS, 1, Serialized)
  226. | {
  227. | CreateDWordField (Arg0, Zero, DVID)
  228. >>> Name (_T_0, Zero)
  229. | Store (DVID, _T_0)
  230. | If (LEqual (_T_0, 0xA0000000))
  231. | {
  232. | Store (0x03, Local0)
  233.  
  234.  
  235. [FAIL]-Use of reserved word (_T_0)
  236.  
  237. Use of reserved word (_T_0)
  238. At line #7762 of DSDT.dsl:
  239.  
  240. | {
  241. | /* 0000 */ 0xA6, 0xFA, 0xDD, 0x3D, 0x1B, 0x36, 0xB4, 0x4E,
  242. | /* 0008 */ 0xA4, 0x24, 0x8D, 0x10, 0x08, 0x9D, 0x16, 0x53
  243. | }))
  244. | {
  245. >>> Name (_T_0, Zero)
  246. | Store (ToInteger (Arg2), _T_0)
  247. | If (LEqual (_T_0, Zero))
  248. | {
  249. | Return (Buffer (One)
  250.  
  251.  
  252. [FAIL]-Use of reserved word (_T_1)
  253.  
  254. Use of reserved word (_T_1)
  255. At line #7892 of DSDT.dsl:
  256.  
  257. | {
  258. | /* 0000 */ 0xED, 0x54, 0x60, 0x37, 0x13, 0xCC, 0x75, 0x46,
  259. | /* 0008 */ 0x90, 0x1C, 0x47, 0x56, 0xD7, 0xF2, 0xD4, 0x5D
  260. | }))
  261. | {
  262. >>> Name (_T_1, Zero)
  263. | Store (ToInteger (Arg2), _T_1)
  264. | If (LEqual (_T_1, Zero))
  265. | {
  266. | Return (Buffer (One)
  267.  
  268.  
  269. [FAIL]-Use of reserved word (_T_0)
  270.  
  271. Use of reserved word (_T_0)
  272. At line #8004 of DSDT.dsl:
  273.  
  274. | {
  275. | /* 0000 */ 0xA6, 0xFA, 0xDD, 0x3D, 0x1B, 0x36, 0xB4, 0x4E,
  276. | /* 0008 */ 0xA4, 0x24, 0x8D, 0x10, 0x08, 0x9D, 0x16, 0x53
  277. | }))
  278. | {
  279. >>> Name (_T_0, Zero)
  280. | Store (ToInteger (Arg2), _T_0)
  281. | If (LEqual (_T_0, Zero))
  282. | {
  283. | Return (Buffer (One)
  284.  
  285.  
  286. [FAIL]-Use of reserved word (_T_1)
  287.  
  288. Use of reserved word (_T_1)
  289. At line #8134 of DSDT.dsl:
  290.  
  291. | {
  292. | /* 0000 */ 0xED, 0x54, 0x60, 0x37, 0x13, 0xCC, 0x75, 0x46,
  293. | /* 0008 */ 0x90, 0x1C, 0x47, 0x56, 0xD7, 0xF2, 0xD4, 0x5D
  294. | }))
  295. | {
  296. >>> Name (_T_1, Zero)
  297. | Store (ToInteger (Arg2), _T_1)
  298. | If (LEqual (_T_1, Zero))
  299. | {
  300. | Return (Buffer (One)
  301.  
  302.  
  303. [PASS]-Tested table DSDT.dsl
  304.  
  305. [PASS]-Tested table SSDT1.dsl
  306.  
  307. [WARN]-Not all control paths return a value (A065)
  308.  
  309. Not all control paths return a value (A065)
  310. At line #240 of SSDT2.dsl:
  311.  
  312. | }
  313. |
  314. | Return (Local1)
  315. | }
  316. |
  317. >>> Method (A065, 2, Serialized)
  318. | {
  319. | OperationRegion (PMIO, SystemIO, 0x0CD6, 0x02)
  320. | Field (PMIO, ByteAcc, NoLock, Preserve)
  321. | {
  322.  
  323.  
  324. [WARN]-Not all control paths return a value (A058)
  325.  
  326. Not all control paths return a value (A058)
  327. At line #881 of SSDT2.dsl:
  328.  
  329. | 0x00,
  330. | 0x00
  331. | })
  332. | Name (A063, 0x00)
  333. | Name (A064, 0x00)
  334. >>> Method (A058, 1, Serialized)
  335. | {
  336. | Store (0x00, A063)
  337. | Store (0x00, A064)
  338. | Store (ShiftLeft (Add (Arg0, 0x02), 0x03), Local1)
  339.  
  340.  
  341. [WARN]-Called method may not always return a value
  342.  
  343. Called method may not always return a value
  344. At line #888 of SSDT2.dsl:
  345.  
  346. | Store (0x00, A063)
  347. | Store (0x00, A064)
  348. | Store (ShiftLeft (Add (Arg0, 0x02), 0x03), Local1)
  349. | If (LEqual (Arg0, 0x06))
  350. | {
  351. >>> Store (A065 (0x00, 0x00), Index (A062, 0x00))
  352. | A065 (0x00, 0x01)
  353. | Return (0x00)
  354. | }
  355. |
  356.  
  357.  
  358. [WARN]-Not all control paths return a value (A061)
  359.  
  360. Not all control paths return a value (A061)
  361. At line #925 of SSDT2.dsl:
  362.  
  363. | A059 (Add (Local2, Local4), A063, Not (0x03), 0x00)
  364. | Increment (Local4)
  365. | }
  366. | }
  367. |
  368. >>> Method (A061, 1, Serialized)
  369. | {
  370. | Store (0x00, A063)
  371. | Store (0x00, A064)
  372. | If (LEqual (Arg0, 0x06))
  373.  
  374.  
  375. [FAIL]-syntax error, unexpected PARSEOP_SLEEP, expecting ',' or ')'
  376.  
  377. syntax error, unexpected PARSEOP_SLEEP, expecting ',' or ')'
  378. At line #1176 of SSDT2.dsl:
  379.  
  380. | If (LEqual (Local2, 0x07))
  381. | {
  382. | If (CondRefOf (\_SB.ALIC, Local6))
  383. | {
  384. | Store (ShiftLeft (Add (Arg0, 0x02), 0x03), Local1)
  385. >>> \_SB.ALIC (Local1, 0x00, Sleep (0x02), \_SB.ALIC (Local1, 0x01, Store (0x00,
  386. | Local3), Store (0x01, Local2), Continue, Store (0x04, Local2)), If (LEqual (Local2,
  387. | 0x05))
  388. | {
  389. | Store (0x01, Local4)
  390.  
  391.  
  392. [FAIL]-syntax error, unexpected PARSEOP_CONTINUE, expecting ',' or ')'
  393.  
  394. syntax error, unexpected PARSEOP_CONTINUE, expecting ',' or ')'
  395. At line #1177 of SSDT2.dsl:
  396.  
  397. | {
  398. | If (CondRefOf (\_SB.ALIC, Local6))
  399. | {
  400. | Store (ShiftLeft (Add (Arg0, 0x02), 0x03), Local1)
  401. | \_SB.ALIC (Local1, 0x00, Sleep (0x02), \_SB.ALIC (Local1, 0x01, Store (0x00,
  402. >>> Local3), Store (0x01, Local2), Continue, Store (0x04, Local2)), If (LEqual (Local2,
  403. | 0x05))
  404. | {
  405. | Store (0x01, Local4)
  406. | Store (0x00, Local2)
  407.  
  408.  
  409. [FAIL]-syntax error, unexpected ')'
  410.  
  411. syntax error, unexpected ')'
  412. At line #1177 of SSDT2.dsl:
  413.  
  414. | {
  415. | If (CondRefOf (\_SB.ALIC, Local6))
  416. | {
  417. | Store (ShiftLeft (Add (Arg0, 0x02), 0x03), Local1)
  418. | \_SB.ALIC (Local1, 0x00, Sleep (0x02), \_SB.ALIC (Local1, 0x01, Store (0x00,
  419. >>> Local3), Store (0x01, Local2), Continue, Store (0x04, Local2)), If (LEqual (Local2,
  420. | 0x05))
  421. | {
  422. | Store (0x01, Local4)
  423. | Store (0x00, Local2)
  424.  
  425.  
  426. [FAIL]-syntax error, unexpected ','
  427.  
  428. syntax error, unexpected ','
  429. At line #1182 of SSDT2.dsl:
  430.  
  431. | Local3), Store (0x01, Local2), Continue, Store (0x04, Local2)), If (LEqual (Local2,
  432. | 0x05))
  433. | {
  434. | Store (0x01, Local4)
  435. | Store (0x00, Local2)
  436. >>> }, If (LEqual (Local2, 0x00))
  437. | {
  438. | Store (0x01, A026)
  439. | A037 ()
  440. | Store (0x08, Local2)
  441.  
  442.  
  443. [FAIL]-syntax error, unexpected ')'
  444.  
  445. syntax error, unexpected ')'
  446. At line #1187 of SSDT2.dsl:
  447.  
  448. | }, If (LEqual (Local2, 0x00))
  449. | {
  450. | Store (0x01, A026)
  451. | A037 ()
  452. | Store (0x08, Local2)
  453. >>> })
  454. | }
  455. | }
  456. | }
  457. |
  458.  
  459.  
  460. [PASS]-Tested table SSDT2.dsl
  461.  
  462. =================================================
  463. * Plugin name: pciresource
  464. * Result: FAIL
  465.  
  466. * Title: Validate assigned PCI resources
  467. * 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.
  468. ================================================
  469.  
  470. [FAIL]-HPET resources incorrect
  471.  
  472. hpet_resources: 0xfed00000 is busy
  473.  
  474. =================================================
  475. * Plugin name: dmi
  476. * Result: FAIL
  477.  
  478. * Title: DMI information check
  479. * Description: This test checks the DMI/SMBIOS tables for common errors.
  480. ================================================
  481.  
  482. [FAIL]-No SMBIOS nor DMI entry point found.
  483.  
  484. [FAIL]-No SMBIOS nor DMI entry point found.
  485.  
  486. [FAIL]-No SMBIOS nor DMI entry point found.
  487.  
  488. [FAIL]-No SMBIOS nor DMI entry point found.
  489.  
  490. [FAIL]-No SMBIOS nor DMI entry point found.
  491.  
  492. [FAIL]-No SMBIOS nor DMI entry point found.
  493.  
  494. [FAIL]-No SMBIOS nor DMI entry point found.
  495.  
  496. [FAIL]-No SMBIOS nor DMI entry point found.
  497.  
  498. [FAIL]-No SMBIOS nor DMI entry point found.
  499.  
  500. [FAIL]-No SMBIOS nor DMI entry point found.
  501.  
  502. [FAIL]-No SMBIOS nor DMI entry point found.
  503.  
  504. [FAIL]-No SMBIOS nor DMI entry point found.
  505.  
  506. [FAIL]-No SMBIOS nor DMI entry point found.
  507.  
  508. [FAIL]-No SMBIOS nor DMI entry point found.
  509.  
  510. [FAIL]-No SMBIOS nor DMI entry point found.
  511.  
  512. [FAIL]-No SMBIOS nor DMI entry point found.
  513.  
  514. [FAIL]-No SMBIOS nor DMI entry point found.
  515.  
  516. [FAIL]-No SMBIOS nor DMI entry point found.
  517.  
  518. [FAIL]-No SMBIOS nor DMI entry point found.
  519.  
  520. [FAIL]-No SMBIOS nor DMI entry point found.
  521.  
  522. [FAIL]-No SMBIOS nor DMI entry point found.
  523.  
  524. [FAIL]-No SMBIOS nor DMI entry point found.
  525.  
  526. [FAIL]-No SMBIOS nor DMI entry point found.
  527.  
  528. [FAIL]-No SMBIOS nor DMI entry point found.
  529.  
  530. [FAIL]-No SMBIOS nor DMI entry point found.
  531.  
  532. [FAIL]-No SMBIOS nor DMI entry point found.
  533.  
  534. [FAIL]-No SMBIOS nor DMI entry point found.
  535.  
  536. [FAIL]-No SMBIOS nor DMI entry point found.
  537.  
  538. [FAIL]-No SMBIOS nor DMI entry point found.
  539.  
  540. [FAIL]-No SMBIOS nor DMI entry point found.
  541.  
  542. [FAIL]-No SMBIOS nor DMI entry point found.
  543.  
  544. [FAIL]-No SMBIOS nor DMI entry point found.
  545.  
  546. [FAIL]-No SMBIOS nor DMI entry point found.
  547.  
  548. [FAIL]-No SMBIOS nor DMI entry point found.
  549.  
  550. [FAIL]-No SMBIOS nor DMI entry point found.
  551.  
  552. [FAIL]-No SMBIOS nor DMI entry point found.
  553.  
  554. [FAIL]-No SMBIOS nor DMI entry point found.
  555.  
  556. [FAIL]-No SMBIOS nor DMI entry point found.
  557.  
  558. [FAIL]-No SMBIOS nor DMI entry point found.
  559.  
  560. [FAIL]-No SMBIOS nor DMI entry point found.
  561.  
  562. [FAIL]-No SMBIOS nor DMI entry point found.
  563.  
  564. [FAIL]-No SMBIOS nor DMI entry point found.
  565.  
  566. [FAIL]-No SMBIOS nor DMI entry point found.
  567.  
  568. [FAIL]-No SMBIOS nor DMI entry point found.
  569.  
  570. [FAIL]-No SMBIOS nor DMI entry point found.
  571.  
  572. [FAIL]-No SMBIOS nor DMI entry point found.
  573.  
  574. [FAIL]-No SMBIOS nor DMI entry point found.
  575.  
  576. [FAIL]-No SMBIOS nor DMI entry point found.
  577.  
  578. [FAIL]-No SMBIOS nor DMI entry point found.
  579.  
  580. [FAIL]-No SMBIOS nor DMI entry point found.
  581.  
  582. [FAIL]-No SMBIOS nor DMI entry point found.
  583.  
  584. [FAIL]-No SMBIOS nor DMI entry point found.
  585.  
  586. [FAIL]-No SMBIOS nor DMI entry point found.
  587.  
  588. [FAIL]-No SMBIOS nor DMI entry point found.
  589.  
  590. =================================================
  591. * Plugin name: maxreadreq
  592. * Result: WARN
  593.  
  594. * Title: PCI Express MaxReadReq tuning
  595. * Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
  596. ================================================
  597.  
  598. [WARN]-MaxReadReq for device pci://00:00:01.0 is low (128)
  599.  
  600. [WARN]-MaxReadReq for device pci://00:00:01.1 is low (128)
  601.  
  602. =================================================
  603. * Plugin name: thermal_trip
  604. * Result: WARN
  605.  
  606. * Title: ACPI passive thermal trip points
  607. * Description: This test determines if the passive trip point works as expected.
  608. ================================================
  609.  
  610. [WARN]-No thermal zones found.
  611.  
  612. =================================================
  613. * Plugin name: fan
  614. * Result: WARN
  615.  
  616. * Title: Fan tests
  617. * Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
  618. ================================================
  619.  
  620. [WARN]-No fan information present
  621.  
  622. =================================================
  623. * Plugin name: cpufreq
  624. * Result: WARN
  625.  
  626. * Title: CPU frequency scaling tests (1-2 mins)
  627. * 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:
  628. 1) Each processor has the same number of frequency states
  629. 2) Higher advertised frequencies have a higher performance
  630. 3) No duplicate frequency values are reported by the BIOS
  631. 4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  632. 5) Is BIOS wrongly doing Sw_Any P-state coordination across cores
  633.  
  634. ================================================
  635.  
  636. [WARN]-Frequency scaling not supported
  637.  
  638. =================================================
  639. * Plugin name: chk_hpet
  640. * Result: WARN
  641.  
  642. * Title: HPET configuration test
  643. * 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.
  644. ================================================
  645.  
  646. [WARN]-HPET driver in the kernel is enabled, inaccurate results follow.
  647.  
  648. [INFO]-HPET found, VendorID is: 1022
  649.  
  650. =================================================
  651. * Plugin name: edd
  652. * Result: INFO
  653.  
  654. * Title: EDD Boot disk hinting
  655. * 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.
  656. ================================================
  657.  
  658. [INFO]-device 80: The system boots from device 0000:00:14.1 channel: 3 device: 0
  659.  
  660.  
  661. [INFO]-device 80: The boot disk has Linux device name /dev/hdc
  662.  
  663. =================================================
  664. * Plugin name: battery
  665. * Result: INFO
  666.  
  667. * Title: Battery tests
  668. * 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.
  669.  
  670. 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.
  671. ================================================
  672.  
  673. [INFO]-No battery information present
  674.  
  675. =================================================
  676. * Plugin name: acpiinfo
  677. * Result: INFO
  678.  
  679. * Title: General ACPI information
  680. * 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.
  681. ================================================
  682.  
  683. [INFO]-DSDT was compiled by the Intel AML compiler
  684.  
  685. ACPI: DSDT BFD66150, 795D (r2 ALASKA A M I 0 INTL 20051117)
  686.  
  687. =================================================
  688. * Plugin name: DMAR
  689. * Result: INFO
  690.  
  691. * Title: (experimental) DMA Remapping (VT-d) test
  692. * Description: Verify if DMA remapping is sane.
  693. ================================================
  694.  
  695. [INFO]-No DMAR ACPI table found.
  696.  
  697. =================================================
  698. * Plugin name: SUN
  699. * Result: PASS
  700.  
  701. * Title: SUN duplicate test
  702. * 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.
  703. ================================================
  704.  
  705. [PASS]-Tested _SUN ids, successfully found no duplicates
  706.  
  707. =================================================
  708. * Plugin name: virt
  709. * Result: PASS
  710.  
  711. * Title: SVM Virtualization extensions
  712. * Description: This test checks if SVM is set up correctly
  713. ================================================
  714.  
  715. =================================================
  716. * Plugin name: ebda
  717. * Result: PASS
  718.  
  719. * Title: EBDA region
  720. * Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
  721. ================================================
  722.  
  723. [PASS]-EBDA region is correctly reserved in the E820 table.
  724.  
  725. =================================================
  726. * Plugin name: os2gap
  727. * Result: PASS
  728.  
  729. * Title: OS/2 memory hole test
  730. * Description: This test checks if the OS/2 15Mb memory hole is absent
  731. ================================================
  732.  
  733. [PASS]-Successfully found no 15mb memory hole
  734.  
  735. =================================================
  736. * Plugin name: ethernet
  737. * Result: PASS
  738.  
  739. * Title: Ethernet functionality
  740. * 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.
  741.  
  742. 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.
  743. ================================================
  744.  
  745. =================================================
  746. * Plugin name: apicedge
  747. * Result: PASS
  748.  
  749. * Title: (experimental) APIC Edge/Level check
  750. * Description: This test checks if legacy interrupts are edge and PCI interrupts are level
  751. ================================================
  752.  
  753. =================================================
  754. * Plugin name: microcode
  755. * Result: PASS
  756.  
  757. * Title: Processor microcode update
  758. * 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.
  759. ================================================
  760.  
  761.  
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!