![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1003707.1 : Understanding SB2500 Post Diagnostics
PreviouslyPublishedAs 205229 Applies to:Sun Blade 2500 Workstation - Version Not Applicable and laterAll Platforms GoalThis document provides guidance on how to understand what is tested when diag-level configuration variable is set to "max" or "min." FixSteps to Follow When the diag-level configuration variable is set to max, POST enables an extended set of diagnostic-level tests for the SB2500 workstation. The following tests are performed in this order: 1. All CPUs do full memory test 2. Slave CPUs test IO-Bridge0 and IO-Bridge1 3. Master CPU performs an Init of critical resources 4. Master CPU test 5. Master CPU I2C 6. Master CPU memory test 7. Slave CPU test 8. Slave CPU memory test 9. Master CPU test of Slave CPU s memory 10. Slave CPU executes POST from master memory 11. All CPUs test internal cache 12. All CPUs scrub memory 13. Master CPU tests both IO-Bridge0 and IO-Bridge1 When the diag-level variable is set to min, POST enables an abbreviated set of diagnostic-level tests. The following tests are performed in this order: 1. Master CPU performs an Init of critical resources 2. Master CPU test 3. Master CPU I2C 4. Master CPU memory test 5. Slave CPU test 6. Slave CPU memory test 7. Master CPU test of slave CPU s memory 8. Slave CPU executes POST from master memory 9. All CPUs test internal cache 10. All CPUs scrub memory 11. Master CPU tests both IO-Bridge0 and IO-Bridge1 Approximate POST Completion Times CPU Memory diag-level max diag-level min 2 8GB 8 minutes 3 minutes
Attachments This solution has no attachment |
||||||||||||
|