API tools faq
paste
Advertisement
Guest User

Corvalent SB5000P EATX Server Board ACPI test results

a guest
Oct 20th, 2011
159
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.38 KB | None | 0 0
raw download clone embed print report
  1. -------------------------------------------------
  2. Date: Thu Oct 20 16:15: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: 2 Fails, 9 Warns, 9 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:05:00.0) has incorrect attribute uncached write-back
  28.  
  29. Memory range 0xc0000000 to 0xcfffffff (0000:05:00.0) has incorrect attribute uncached write-back
  30.  
  31. [FAIL]-Memory range 0xdc000000 to 0xddffffff (0000:05:00.0) has incorrect attribute uncached write-back
  32.  
  33. Memory range 0xdc000000 to 0xddffffff (0000:05:00.0) has incorrect attribute uncached write-back
  34.  
  35. [FAIL]-Memory range 0xfc000000 to 0xfcffffff (0000:05:00.0) has incorrect attribute write-back
  36.  
  37. Memory range 0xfc000000 to 0xfcffffff (0000:05:00.0) has incorrect attribute write-back
  38.  
  39. [FAIL]-Memory range 0xfdc7c000 to 0xfdc7ffff (0000:05:00.1) has incorrect attribute write-back
  40.  
  41. Memory range 0xfdc7c000 to 0xfdc7ffff (0000:05:00.1) has incorrect attribute write-back
  42.  
  43. [FAIL]-Memory range 0xfdc80000 to 0xfdcfffff (0000:05:00.0) has incorrect attribute write-back
  44.  
  45. Memory range 0xfdc80000 to 0xfdcfffff (0000:05:00.0) has incorrect attribute write-back
  46.  
  47. [FAIL]-Memory range 0xfde60000 to 0xfde7ffff (0000:0a:00.0) has incorrect attribute write-back
  48.  
  49. Memory range 0xfde60000 to 0xfde7ffff (0000:0a:00.0) has incorrect attribute write-back
  50.  
  51. [FAIL]-Memory range 0xfde80000 to 0xfde9ffff (0000:0a:00.0) has incorrect attribute write-back
  52.  
  53. Memory range 0xfde80000 to 0xfde9ffff (0000:0a:00.0) has incorrect attribute write-back
  54.  
  55. [FAIL]-Memory range 0xfdea0000 to 0xfdeaffff (0000:0a:00.0) has incorrect attribute write-back
  56.  
  57. Memory range 0xfdea0000 to 0xfdeaffff (0000:0a:00.0) has incorrect attribute write-back
  58.  
  59. [FAIL]-Memory range 0xfdeb0000 to 0xfdebffff (0000:0a:00.1) has incorrect attribute write-back
  60.  
  61. Memory range 0xfdeb0000 to 0xfdebffff (0000:0a:00.1) has incorrect attribute write-back
  62.  
  63. [FAIL]-Memory range 0xfdec0000 to 0xfdedffff (0000:0a:00.1) has incorrect attribute write-back
  64.  
  65. Memory range 0xfdec0000 to 0xfdedffff (0000:0a:00.1) has incorrect attribute write-back
  66.  
  67. [FAIL]-Memory range 0xfdee0000 to 0xfdefffff (0000:0a:00.1) has incorrect attribute write-back
  68.  
  69. Memory range 0xfdee0000 to 0xfdefffff (0000:0a:00.1) has incorrect attribute write-back
  70.  
  71. [FAIL]-Memory range 0xfdff4000 to 0xfdff7fff (0000:00:1b.0) has incorrect attribute write-back
  72.  
  73. Memory range 0xfdff4000 to 0xfdff7fff (0000:00:1b.0) has incorrect attribute write-back
  74.  
  75. [FAIL]-Memory range 0xfdffb800 to 0xfdffbbff (0000:00:1d.7) has incorrect attribute write-back
  76.  
  77. Memory range 0xfdffb800 to 0xfdffbbff (0000:00:1d.7) has incorrect attribute write-back
  78.  
  79. [FAIL]-Memory range 0xfdffbc00 to 0xfdffbfff (0000:00:1f.2) has incorrect attribute write-back
  80.  
  81. Memory range 0xfdffbc00 to 0xfdffbfff (0000:00:1f.2) has incorrect attribute write-back
  82.  
  83. =================================================
  84. * Plugin name: dmi
  85. * Result: FAIL
  86.  
  87. * Title: DMI information check
  88. * Description: This test checks the DMI/SMBIOS tables for common errors.
  89. ================================================
  90.  
  91. [FAIL]-No SMBIOS nor DMI entry point found.
  92.  
  93. [FAIL]-No SMBIOS nor DMI entry point found.
  94.  
  95. [FAIL]-No SMBIOS nor DMI entry point found.
  96.  
  97. [FAIL]-No SMBIOS nor DMI entry point found.
  98.  
  99. [FAIL]-No SMBIOS nor DMI entry point found.
  100.  
  101. [FAIL]-No SMBIOS nor DMI entry point found.
  102.  
  103. [FAIL]-No SMBIOS nor DMI entry point found.
  104.  
  105. [FAIL]-No SMBIOS nor DMI entry point found.
  106.  
  107. [FAIL]-No SMBIOS nor DMI entry point found.
  108.  
  109. [FAIL]-No SMBIOS nor DMI entry point found.
  110.  
  111. [FAIL]-No SMBIOS nor DMI entry point found.
  112.  
  113. [FAIL]-No SMBIOS nor DMI entry point found.
  114.  
  115. [FAIL]-No SMBIOS nor DMI entry point found.
  116.  
  117. [FAIL]-No SMBIOS nor DMI entry point found.
  118.  
  119. [FAIL]-No SMBIOS nor DMI entry point found.
  120.  
  121. =================================================
  122. * Plugin name: acpicompile
  123. * Result: WARN
  124.  
  125. * Title: DSDT AML verification
  126. * 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.
  127. ================================================
  128.  
  129. [WARN]-Possible operator timeout is ignored
  130.  
  131. Possible operator timeout is ignored
  132. At line #7687 of DSDT.dsl:
  133.  
  134. | Name (XSST, 0x1A)
  135. | Name (XRCT, 0x1C)
  136. | Mutex (MUTE, 0x00)
  137. | Method (RBPE, 1, NotSerialized)
  138. | {
  139. >>> Acquire (MUTE, 0x03E8)
  140. | Add (Arg0, PCIB, Local0)
  141. | OperationRegion (PCFG, SystemMemory, Local0, One)
  142. | Field (PCFG, ByteAcc, NoLock, Preserve)
  143. | {
  144.  
  145.  
  146. [WARN]-Possible operator timeout is ignored
  147.  
  148. Possible operator timeout is ignored
  149. At line #7701 of DSDT.dsl:
  150.  
  151. | Return (XCFG)
  152. | }
  153. |
  154. | Method (RWPE, 1, NotSerialized)
  155. | {
  156. >>> Acquire (MUTE, 0x03E8)
  157. | And (Arg0, 0xFFFFFFFE, Arg0)
  158. | Add (Arg0, PCIB, Local0)
  159. | OperationRegion (PCFG, SystemMemory, Local0, 0x02)
  160. | Field (PCFG, WordAcc, NoLock, Preserve)
  161.  
  162.  
  163. [WARN]-Possible operator timeout is ignored
  164.  
  165. Possible operator timeout is ignored
  166. At line #7716 of DSDT.dsl:
  167.  
  168. | Return (XCFG)
  169. | }
  170. |
  171. | Method (RDPE, 1, NotSerialized)
  172. | {
  173. >>> Acquire (MUTE, 0x03E8)
  174. | And (Arg0, 0xFFFFFFFC, Arg0)
  175. | Add (Arg0, PCIB, Local0)
  176. | OperationRegion (PCFG, SystemMemory, Local0, 0x04)
  177. | Field (PCFG, DWordAcc, NoLock, Preserve)
  178.  
  179.  
  180. [WARN]-Possible operator timeout is ignored
  181.  
  182. Possible operator timeout is ignored
  183. At line #7731 of DSDT.dsl:
  184.  
  185. | Return (XCFG)
  186. | }
  187. |
  188. | Method (WBPE, 2, NotSerialized)
  189. | {
  190. >>> Acquire (MUTE, 0x0FFF)
  191. | Add (Arg0, PCIB, Local0)
  192. | OperationRegion (PCFG, SystemMemory, Local0, One)
  193. | Field (PCFG, ByteAcc, NoLock, Preserve)
  194. | {
  195.  
  196.  
  197. [WARN]-Possible operator timeout is ignored
  198.  
  199. Possible operator timeout is ignored
  200. At line #7745 of DSDT.dsl:
  201.  
  202. | Release (MUTE)
  203. | }
  204. |
  205. | Method (WWPE, 2, NotSerialized)
  206. | {
  207. >>> Acquire (MUTE, 0x03E8)
  208. | And (Arg0, 0xFFFFFFFE, Arg0)
  209. | Add (Arg0, PCIB, Local0)
  210. | OperationRegion (PCFG, SystemMemory, Local0, 0x02)
  211. | Field (PCFG, WordAcc, NoLock, Preserve)
  212.  
  213.  
  214. [WARN]-Possible operator timeout is ignored
  215.  
  216. Possible operator timeout is ignored
  217. At line #7760 of DSDT.dsl:
  218.  
  219. | Release (MUTE)
  220. | }
  221. |
  222. | Method (WDPE, 2, NotSerialized)
  223. | {
  224. >>> Acquire (MUTE, 0x03E8)
  225. | And (Arg0, 0xFFFFFFFC, Arg0)
  226. | Add (Arg0, PCIB, Local0)
  227. | OperationRegion (PCFG, SystemMemory, Local0, 0x04)
  228. | Field (PCFG, DWordAcc, NoLock, Preserve)
  229.  
  230.  
  231. [WARN]-Possible operator timeout is ignored
  232.  
  233. Possible operator timeout is ignored
  234. At line #7775 of DSDT.dsl:
  235.  
  236. | Release (MUTE)
  237. | }
  238. |
  239. | Method (RWDP, 3, NotSerialized)
  240. | {
  241. >>> Acquire (MUTE, 0x03E8)
  242. | And (Arg0, 0xFFFFFFFC, Arg0)
  243. | Add (Arg0, PCIB, Local0)
  244. | OperationRegion (PCFG, SystemMemory, Local0, 0x04)
  245. | Field (PCFG, DWordAcc, NoLock, Preserve)
  246.  
  247.  
  248. [PASS]-Tested table DSDT.dsl
  249.  
  250. =================================================
  251. * Plugin name: maxreadreq
  252. * Result: WARN
  253.  
  254. * Title: PCI Express MaxReadReq tuning
  255. * Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
  256. ================================================
  257.  
  258. [WARN]-MaxReadReq for device pci://00:00:1b.0 is low (128)
  259.  
  260. =================================================
  261. * Plugin name: edd
  262. * Result: WARN
  263.  
  264. * Title: EDD Boot disk hinting
  265. * 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.
  266. ================================================
  267.  
  268. [INFO]-device 80: The system boots from device 0000:00:1f.2 channel: 255 device: 0
  269.  
  270.  
  271. [WARN]-device 80: No matching MBR signature (0x000c2387) found for the boot disk
  272.  
  273. Device sda - signature 0x5d604727
  274.  
  275.  
  276. [INFO]-device 81 is provided by device 0000:00:1d.7 channel: 0 serial_number: 0
  277.  
  278.  
  279. [INFO]-device 81: This disk has Linux device name /dev/sda
  280.  
  281. =================================================
  282. * Plugin name: thermal_trip
  283. * Result: WARN
  284.  
  285. * Title: ACPI passive thermal trip points
  286. * Description: This test determines if the passive trip point works as expected.
  287. ================================================
  288.  
  289. [WARN]-No thermal zones found.
  290.  
  291. =================================================
  292. * Plugin name: fan
  293. * Result: WARN
  294.  
  295. * Title: Fan tests
  296. * Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
  297. ================================================
  298.  
  299. [WARN]-No fan information present
  300.  
  301. =================================================
  302. * Plugin name: cpufreq
  303. * Result: WARN
  304.  
  305. * Title: CPU frequency scaling tests (1-2 mins)
  306. * 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:
  307. 1) Each processor has the same number of frequency states
  308. 2) Higher advertised frequencies have a higher performance
  309. 3) No duplicate frequency values are reported by the BIOS
  310. 4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  311. 5) Is BIOS wrongly doing Sw_Any P-state coordination across cores
  312.  
  313. ================================================
  314.  
  315. [WARN]-Frequency scaling not supported
  316.  
  317. =================================================
  318. * Plugin name: ebda
  319. * Result: WARN
  320.  
  321. * Title: EBDA region
  322. * Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
  323. ================================================
  324.  
  325. [WARN]-E820: EBDA region at 0x9ec00 is not reserved in the E820 table
  326.  
  327. =================================================
  328. * Plugin name: chk_hpet
  329. * Result: WARN
  330.  
  331. * Title: HPET configuration test
  332. * 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.
  333. ================================================
  334.  
  335. [WARN]-HPET driver in the kernel is enabled, inaccurate results follow.
  336.  
  337. [INFO]-HPET found, VendorID is: FFFF
  338.  
  339. [WARN]-Invalid clock period -1, must be non-zero and less than 10^8 fs
  340.  
  341. =================================================
  342. * Plugin name: ethernet
  343. * Result: WARN
  344.  
  345. * Title: Ethernet functionality
  346. * 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.
  347.  
  348. 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.
  349. ================================================
  350.  
  351. [INFO]-Acquired ethernet link after 0 seconds
  352.  
  353. [WARN]-Got no DHCP lease
  354.  
  355. Internet Systems Consortium DHCP Client V3.0.4-RedHat
  356. Copyright 2004-2006 Internet Systems Consortium.
  357. All rights reserved.
  358. For info, please visit http://www.isc.org/sw/dhcp/
  359.  
  360. Listening on LPF/eth0/00:07:b8:dc:89:7e
  361. Sending on LPF/eth0/00:07:b8:dc:89:7e
  362. Sending on Socket/fallback
  363. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
  364. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
  365. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
  366. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
  367. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
  368. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
  369. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
  370. No DHCPOFFERS received.
  371. No working leases in persistent database - sleeping.
  372.  
  373.  
  374. [INFO]-Acquired ethernet link after 0 seconds
  375.  
  376. [PASS]-Got a DHCP lease
  377.  
  378. Internet Systems Consortium DHCP Client V3.0.4-RedHat
  379. Copyright 2004-2006 Internet Systems Consortium.
  380. All rights reserved.
  381. For info, please visit http://www.isc.org/sw/dhcp/
  382.  
  383. Listening on LPF/eth1/00:07:b8:dc:89:7f
  384. Sending on LPF/eth1/00:07:b8:dc:89:7f
  385. Sending on Socket/fallback
  386. DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
  387. DHCPOFFER from 140.178.153.246
  388. DHCPREQUEST on eth1 to 255.255.255.255 port 67
  389. DHCPACK from 140.178.153.246
  390. bound to 140.178.153.202 -- renewal in 69906 seconds.
  391.  
  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 Intel AML compiler
  414.  
  415. ACPI: DSDT 7FFE0470, 65AE (r1 Z250V Z250V014 14 INTL 20051117)
  416.  
  417. =================================================
  418. * Plugin name: DMAR
  419. * Result: INFO
  420.  
  421. * Title: (experimental) DMA Remapping (VT-d) test
  422. * Description: Verify if DMA remapping is sane.
  423. ================================================
  424.  
  425. [INFO]-No DMAR ACPI table found.
  426.  
  427. =================================================
  428. * Plugin name: pciresource
  429. * Result: PASS
  430.  
  431. * Title: Validate assigned PCI resources
  432. * 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.
  433. ================================================
  434.  
  435. =================================================
  436. * Plugin name: SUN
  437. * Result: PASS
  438.  
  439. * Title: SUN duplicate test
  440. * 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.
  441. ================================================
  442.  
  443. [PASS]-Tested _SUN ids, successfully found no duplicates
  444.  
  445. =================================================
  446. * Plugin name: virt
  447. * Result: PASS
  448.  
  449. * Title: VT/VMX Virtualization extensions
  450. * Description: This test checks if VT/VMX is set up correctly
  451. ================================================
  452.  
  453. =================================================
  454. * Plugin name: os2gap
  455. * Result: PASS
  456.  
  457. * Title: OS/2 memory hole test
  458. * Description: This test checks if the OS/2 15Mb memory hole is absent
  459. ================================================
  460.  
  461. [PASS]-Successfully found no 15mb memory hole
  462.  
  463. =================================================
  464. * Plugin name: apicedge
  465. * Result: PASS
  466.  
  467. * Title: (experimental) APIC Edge/Level check
  468. * Description: This test checks if legacy interrupts are edge and PCI interrupts are level
  469. ================================================
  470.  
  471. =================================================
  472. * Plugin name: microcode
  473. * Result: PASS
  474.  
  475. * Title: Processor microcode update
  476. * 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.
  477. ================================================
  478.  
  479.  
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!