Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1006927.1 : Sun Fire[TM] 12K/15K/20K/25K : "EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC" from SMS1.6 POST run
PreviouslyPublishedAs 209596 Description Hpost Overview: The HOST POST (hpost) application is responsible for probing, testing and configuring the hardware of a Sun Fire[TM] 12K/15K domain, preparing it for use by the OpenBoot[TM] PROM and the Solaris[TM] Operating Environment (Solaris OS). The Sun Fire 15K/12K platform's /opt/SUNWSMS/bin/hpost executable houses both the power-on self-test(POST) as well as the necessary logic involved in sequencing POST's operations. Steps to Follow Error description: Sun Fire 12K/15K/20K/25K platform with System Controller loaded with SMS 1.6 observed the following POST log verbiage when high level POST (level 64 or greater) is applied to resident domains. For example, a domain with the following resources assigned: SB5 On V3CPU Active Passed D IO5 On HPCI+ Active Passed D When subjected to a level 64 POST run will report the following: # hpost version 1.6 GENERIC Apr 17 2006 11:33:03 # libxcpost.so v. 1.6 GENERIC Apr 17 2006 11:17:26 # pid = 17890 level = 64 verbose_level = 20 : stage pci_lpost: Test all L1 I/O boards... Performing ASIC config with bus config a/d/r = 333... Slot0 in domain: 00020 Slot1 in domain: 00020 EXBs in use: 17F19 pcilpost.elf Version 5.20.0 Build 15.1 I/F 12 is newest supported Slot SB5: EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC Slot IO5: EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC Slot SB5: EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC Slot IO5: EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC : The "EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC" logs reported from the level 64 POST run had stemmed from an incorrect behavior on the part the hpost routine responsible for implementing the PCI IOC ECC diagnostics cycle. Given that this specific diagnostics cycle is only implemented on level 64 (or greater) POST runs, it would mean that "EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC" logs would only be observed on POST runs that are initiated at level 64 (or greater). As observed from the above level 64 POST run logs - the "EpiSchizoEccR1_sc_tfunc(): ALERT: DXs do not report seeing forced ECC" verbiage has no material impact on the outcome of the POST run -- the high level POST run completed w/o any apparent difference in the expected outcome. Hence, the recommended course of action against the above informational messages logged to the POST run logs is to ignore the "ALERT" messages. These messages are filtered with Patch ID 124319-01 or above. Product Sun Fire E25K Server Sun Fire E20K Server Sun Fire 15K Server Sun Fire 12K Server EpiSchizoEccR1_sc_tfunc, DX, ALERT, ECC, hpost, SMS 1.6, post, asic_dx_eccerr_ctl, starcat, amazon Previously Published As 87067 Change History Reviewed by ESG Content Team on Nov 25, 2009 Date: 2009-11-25 User Name: Cootware Action: Updated Fix in "steps-to-follow" Updated summaries to fix conversion issues. Date: 2006-09-29 User Name: 94145 Action: Add Comment Comment: Looks good to me Version: 0 Date: 2006-09-29 User Name: 97961 Action: Approved Comment: - Converted to STM formatting for better readability - Applied trademarking where it is missing - Made simple sentence/grammatical corrections Version: 3 Product_uuid d842dd03-059b-11d8-84cb-080020a9ed93|Sun Fire E25K Server 1404a2d3-059a-11d8-84cb-080020a9ed93|Sun Fire E20K Server 29e4659c-0a18-11d6-9fa1-e67bbc033df8|Sun Fire 15K Server 077fd4c5-df8f-4320-ad69-7d01603a674d|Sun Fire 12K Server Attachments This solution has no attachment |
||||||||||||
|