Patch-ID# 110304-07 Keywords: Starfire SSP Synopsis: SSP 3.4: Updates for hpost, redx, and autoconfig Date: Sep/20/2002 Install Requirements: See Special Install Instructions Solaris Release: 2.6 7 8 SunOS Release: 5.6 5.7 5.8 Unbundled Product: System Service Processor Unbundled Release: 3.4 Xref: Topic: SSP 3.4: Updates for hpost, redx, and autoconfig Relevant Architectures: sparc BugId's fixed with this patch: 4268088 4310528 4360376 4362960 4366498 4397802 4401066 4402889 4415072 4417673 4423595 4425374 4425375 4433894 4458358 4518294 4614733 Changes incorporated in this version: 4310528 4401066 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /opt/SUNWssp/bin/acfg_check /opt/SUNWssp/bin/acfg_update_db /opt/SUNWssp/lib/libxpost.so /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/bin/hpost /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/bin/redx /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/rn.elf /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/stage0.elf /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/stage1.elf /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/stage2.elf /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/stage3.elf /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/stage4.elf /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/stage5.elf /opt/SUNWssp/release/Ultra-Enterprise-10000/5/5/1/hostobjs/stagei.elf /var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/board/sysboard/chip.ids /var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/board/sysboard/rev1/BS1.chips /var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/board/sysboard/rev1/BS2.chips /var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/board/sysboard/rev1/BS3.chips /var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/chip/sombra/rev1/bypass.fields /var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/chip/sombra/rev1/id.fields /var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/chip/sombra/rev1/sombra.chains Problem Description: 4310528 Bringup with centerplane configuration shows errors in post test for IOC's 4401066 Need to identify mirrored SRAM cpu modules after bringup/DR (from 110304-06) 4401066 Need to identify mirrored SRAM cpu modules after bringup/DR 4518294 Error message confuses customers and needs to be changed 4614733 Enhancement needed to handle rev0 & rev1 mirrored tag srams (from 110304-05) 4458358 POST ecache TAG test enhancement needed. (from 110304-04) 4415072 "Bogus clk_mode" errors during phase proc1 for Arbstop/Recordstop/Timeout 4417673 hpost phase timeout value incorrect for 64-proc configurations 4423595 Fix ecache parity testing to match Sunfire test patterns 4425374 Enhance "unexpected foreign PIO" and "MC Timeout" messaging 4425375 Improve handling of long user input lines 4433894 autoconfig WARNING for new MSRAM ID needs special change (from 110304-03) 4397802 wfail does not FAIL procs for CIC "Coherent error processor " 4402889 Bringup does not verify that bootproc returned from HPOST is in domain. (from 110304-02) 4268088 Modify POST/SSP to Reflect Processor Speed of 466MHz 4366498 Create new hpost ecache tests for new ecache SRAM. (from 110304-01) 4360376 autoconfig changes required to support new ecache srams 4362960 POST changes required to support new ecache SRAM Patch Installation Instructions: -------------------------------- Refer to the Install.info file within the patch for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below. Special Install Instructions: ----------------------------- *** PLEASE SEE THE CURRENT VERSION OF THE SSP3.4 INSTALLATION GUIDE AND RELEASE NOTES *** Installation Issues The information presented in this section is for use by authorized service providers only. ----------- Revision -06 of this patch gives authorized Sun personnel the ability to track processor modules that have mirrored SRAM (MSRAM) ecache. This patch revision contains changes to autoconfig(1M) and hpost(1M), which enable tracking of MSRAM processor modules. Another separate but related patch involves a change to obp(1M) for MSRAM detection. The obp(1M) patch number is: 110316-04 (OBP) If you use OBP patch 110316-04, it is suggested that you also apply hpost patch 110304-06 (revision -06 of this patch) to your SSP, so that the new MSRAM tracking information can be properly handed off from hpost to OBP. However, OBP patch 110316-04 can be applied to an SSP and function normally without the application of hpost patch 110304-06. If you apply the OPB patch but not the hpost patch, the MSRAM tracking information will not be available from hpost for handoff to OBP. ----------- Revision -01 of this patch involves special mirrored SRAM (MSRAM) processor modules that have the following part numbers: 501-5838 501-5866 501-6008 Note: If you are using system boards that do NOT include any of the specific processor module part numbers listed above, do NOT perform the "autoconfig steps" described below. If you ARE using system boards that DO have any of the specific processor module part numbers listed above, you MUST perform the following "autoconfig steps" after installing this patch: autoconfig steps: *** NOTE: Before running autoconfig(1M), shut down the operating environment of the affected domain first. autoconfig(1M) performs a destructive JTAG probe of every JTAG ring of the target system board, the processor modules of the target system board, and the mezzanine boards of the target system board. Failure to gracefully shut down the domain operating environment before running autoconfig results in the unintended crashing of that domain, which in turn can result in data corruption. autoconfig(1M) can be run in one of two modes: 1) With a specific system board as an argument OR 2) Without arguments Running autoconfig with a "sysboard" argument causes autoconfig to be run only against the chosen "sysboard". Running autoconfig(1M) with no arguments causes autoconfig to be run against EVERY system board in the platform. In the latter case, ALL domains in the Sun Enterprise 10000 platform must be gracefully shut down first. See the autoconfig(1M) man page for more information. *** 1. On the main SSP, disable failover: setfailover off. 2. Install the patch on the main SSP. 3. Install the patch on the spare SSP (if present). 4. Run the autoconfig(1M) command for each system board that contains mirrored SRAM processor modules. You must run autoconfig(1M) for these system boards before the boards run POST. The POST changes included in this patch require the scan and configuration updates that result from running autoconfig(1M). 5. After running autoconfig(1M) on these system boards, reboot the SSP, which restarts the control board server (CBS). The SSP configures the JTAG database to support the mirrored SRAM processor modules. From this point forward, you can successfully run the hpost(1M) and bringup(1M) commands on system boards that contain mirrored SRAM processor modules. 6. On the main SSP, make sure that SSP failover is enabled. If not, enable SSP failover: setfailover on. 7. Propagate the autoconfig changes to the spare SSP: setdatasync backup. README -- Last modified date: Friday, September 20, 2002