Document fins/I0562-1
FIN #: I0562-1
SYNOPSIS: Autoconfig syntax error can cause global arbstops.
DATE: 03/31/2000
KEYWORDS: Autoconfig syntax error can cause global arbstops.
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: Autoconfig syntax error can cause global arbstops.
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: Autoconfig on all E10000 systems
PRODUCT CATEGORY: Server / SW Admin
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- E10000 All Sun Enterprise 10000 Server -
- HPC10000 All Sun Enterprise 10000 Server -
X-Options Affected
------------------
- - - - -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
- - -
REFERENCES:
BugId: 4314144
PatchId: 
109076 (SSP 3.3 - Starfire SSP 3.3 autoconfig)
109047 (SSP 3.2 - Starfire SSP 3.2 autoconfig)
109040 (SSP 3.1.1 - Starfire autoconfig arbstop)
PROBLEM DESCRIPTION:
This problem could cause a Global Arbstop which would result in
downtime for every running domain on an E10000 systems platform.
When running autoconfig with more than one argument, autoconfig will
begin to run on every board of an E10000 systems platform. This could
result in an arbstop of every running domain. Autoconfig should report
a problem with the options rather than running on the entire platform.
The problem typically occurs when running autoconfig on a system board
(autoconfig sysboardn). It is possible to mistakenly enter a space
between the sysboard option and the number of the system board.
The arbstop dump for the first domain to crash will contain
"Nack/Abort" as shown on the following error message:
Created Fri Feb 18 13:12:53 2000
By hpost v. 3.1.1 Jun 14 1999 19:03:19 executing as pid=6679
On ssp name = southpark-ssp2.SD_Lab.West.Sun.COM
HOSTNAME = cartman
platform_name = southpark
Boardmask = 30020 -D option
Edd-Arbstop-Dump
There were 0 errors encountered while creating this dump.
redxl> wfail
LAARB 5 ErrorCSR1[65:0] = 0 00000000 3FC00003
ErrCSR1[29:22,1:0]: Arbstop + Recordstop, requested by all 4 GAARBs
GAARB 0 ErrorCSR1[65:0] = 0 40000000 40000003
ErrCSR1[1:0]: Arbstop + Recordstop detected
ErrCSR1[30]: GDARB 0 Error Detected (GAARB)
ErrCSR1[62]: GDARB 1 Error Detected (GAARB)
GAARB 0 ArbStopLog[15:0] = E566 RecordStopLog[15:0] = E567
GAARB 0 ParErrLog[15:0] = 0001
GAARB 0 N/A_ParErrLog[15:0] = 0001
GDARB 0 Sysboard Request Parity Error Mask [15:0] = 0001
FAIL LDPATH 0.0: Arbstop detected by gdarb.
NOTE: FAIL attributed to board 0 not in dump
GDARB 1 Sysboard Request Parity Error Mask [15:0] = 0001
FAIL LDPATH 0.1: Arbstop detected by gdarb.
NOTE: FAIL attributed to board 0 not in dump
FAIL CIC 0.0: Arbstop detected by gaarb.
NOTE: FAIL attributed to board 0 not in dump
GAARB 1 ErrorCSR1[65:0] = 0 40000000 40000003
ErrCSR1[1:0]: Arbstop + Recordstop detected
ErrCSR1[30]: GDARB 0 Error Detected (GAARB)
ErrCSR1[62]: GDARB 1 Error Detected (GAARB)
GAARB 1 ArbStopLog[15:0] = E566 RecordStopLog[15:0] = E566
GAARB 1 ParErrLog[15:0] = 0001
GAARB 1 N/A_ParErrLog[15:0] = 0001
FAIL CIC 0.1: Arbstop detected by gaarb.
NOTE: FAIL attributed to board 0 not in dump
GAARB 2 ErrorCSR1[65:0] = 1 40000000 C0000003
ErrCSR1[1:0]: Arbstop + Recordstop detected
ErrCSR1[30]: GDARB 0 Error Detected (GAARB)
ErrCSR1[31]: Nack/Abort Phase Error (GAARB)
ErrCSR1[62]: GDARB 1 Error Detected (GAARB)
ErrCSR1_hi[0]: Nack/Abort Domain Error (GAARB)
GAARB 2 ArbStopLog[15:0] = E566 RecordStopLog[15:0] = E566
GAARB 2 ParErrLog[15:0] = 0001
GAARB 2 InQOflowLog[15:0] = 0001
GAARB 2 N/A_ParErrLog[15:0] = 0001
GAARB 2 N/A_ErrData[15:0][1:0] = 00000003
FAIL CIC 0.2: Arbstop detected by gaarb.
NOTE: FAIL attributed to board 0 not in dump
GAARB 3 ErrorCSR1[65:0] = 0 40000000 40000003
ErrCSR1[1:0]: Arbstop + Recordstop detected
ErrCSR1[30]: GDARB 0 Error Detected (GAARB)
ErrCSR1[62]: GDARB 1 Error Detected (GAARB)
GAARB 3 ArbStopLog[15:0] = E566 RecordStopLog[15:0] = E566
GAARB 3 ParErrLog[15:0] = 0001
GAARB 3 N/A_ParErrLog[15:0] = 0001
FAIL CIC 0.3: Arbstop detected by gaarb.
NOTE: FAIL attributed to board 0 not in dump
The autoconfig command does not sufficiently parse the arguments
passed to it. If the number of arguments is not equal to 1,
autoconfig will run as if no arguments were supplied. The result
is that autoconfig will run on every board in the system.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| X | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
Once the patches are available, they should be installed on the SSP to
avoid this potential hazard. If the patches are not available or not
installed, care must be taken when running the autoconfig command.
Whenever it becomes necessary to run autoconfig on a system board, such
as when a new part is introduced to a platform, be sure to use the
proper syntax.
The proper syntax to run autoconfig on a system board would be
autoconfig sysboardN, where N is the number of the system board. Note
the fact that sysboardN is one word and that a space should not be
inserted between "sysboard" and the number of the system board.
Follow this instruction when installing the patch;
For Solaris 2.0-2.6 releases, refer to the Install.info file and/or
the README within the patch for instructions on using the generic
'installpatch' and 'backoutpatch' scripts provided with each patch.
For Solaris 7-8 release, refer to the man pages for instructions on
using 'patchadd' and 'patchrm' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions.
COMMENTS:
--------------------------------------------------------------------------
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "Enterprise Services Documenta-
tion" and click on "FIN & FCO attachments", then choose the
appropriate
folder, FIN or FCO. This will display supporting directories/files for
FINs or FCOs.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------
with "FIN/FCO INDEX as of mm/dd/yy" in Subject Header
Copyright (c) 1997-2003 Sun Microsystems, Inc.