Sun Fire E25K Server
 
Sun Fire E20K Server
 
Sun Fire 12K Server
 
Sun Fire 15K Server
 

GCS>Sun Microsystems>Servers>High-End Servers
 

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.

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.

This solution has no attachment