Document fins/I0864-1
FIN #: I0864-1
SYNOPSIS: Certain multi-processor systems using OBP 4.6.{0-6} may be unable to
boot Solaris 9 Update 1 or later
DATE: Aug/26/02
KEYWORDS: Certain multi-processor systems using OBP 4.6.{0-6} may be unable to
boot Solaris 9 Update 1 or later
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: Certain multi-processor systems using OBP 4.6.{0-6} may be
unable to boot Solaris 9 Update 1 or later.
Sun Alert: No
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: Sun Blade 1000/2000, Sun Fire 280R, Sun Fire V880/V480
Netra 20
PRODUCT CATEGORY: Software / Service
PRODUCTS AFFECTED:
Systems Affected
------- --------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- A28 ALL Sun Blade 1000 -
- A29 ALL Sun Blade 2000 -
- A30 ALL Sun Fire V880 -
- A35 ALL Sun Fire 280R -
- A37 ALL Sun Fire V480 -
- N28 ALL Netra 20 -
X-options Affected
--------- --------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- - - - -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
- - -
REFERENCES:
BugId: 4713787 - Excalibur with 2 cpu's hangs on reboot.
4718514 - init interrupt state back to idle on safari platforms.
PatchID: 
111292 - OBP 4.6.6 for Sun Blade 1000, Sun Blade 2000, Sun Fire
280R, Netra 20.
112186 - OBP 4.6.3 for Sun Fire V880.
113034 - OBP 4.6.4 for Sun Fire V480.
111292 - OBP 4.6.7 for Sun Blade 1000, Sun Blade 2000, Sun Fire
280R, Netra 20.
112186 - OBP 4.6.7 for Sun Fire V880.
113034 - OBP 4.6.7 for Sun Fire V480.
PROBLEM DESCRIPTION:
Multiple-CPU systems based on the Safari Bus which run OBP version
4.6.{0-6} and Solaris 9 Update 1 (09/02) or later versions may fail to
boot due to an interrupt problem. On Sun Blade 1000 and Sun Blade 2000
systems, a boot of Solaris will hang when the second CPU is brought
online. Other Safari Bus platforms running OBP 4.6.{0-6} may also be
affected by this issue, although no failures have been reported.
This issue affects the following systems which utilize the Safari Bus:
Sun Blade 1000 Sun Blade 2000 Sun Fire V880 Sun Fire 280R Sun Fire
V480 Netra 20
These platforms are only affected with the specific configuration of
OBP version 4.6.{0-6}, running multiple CPUs, and Solaris 9 09/02
or later. Only those customers who have explicitly installed Patches
111292, 112186, or 113034 (the patches containing OBP
4.6.{0-6}), are affected. No systems configured at Sun Manufacturing
are affected by this issue.
To determine the system OBP version, use either 'prtdiag' from the Unix
prompt or '.version' from the OBP prompt.
# /usr/platform/platform-name/sbin/prtdiag -v | grep OBP
OBP 4.6.6 2002/06/04 17:36 POST 4.6.1 2002/05/10 14:05
ok .version
Release 4.6 Version 6 created 2002/06/04 17:36
OBP 4.6.6 2002/06/04 17:36
POST 4.6.1 2002/05/10 14:05
The Solaris version and installed patches can be determined by using
'uname -a' and 'showrev -p'.
# uname -a
SunOS plxpig 5.9 Generic sun4u sparc
# showrev -p | grep 111292
In OBP 4.6.0.build_08 an interrupt state register was changed to start
in the PENDING state instead of the IDLE state upon initialization.
There are several places in the PCI driver that depend on the old
behavior, and this causes the system hang. The trigger is when the
second CPU comes online and this results in an interrupt
redistribution.
Because of the severity of the problem on Sun Blade 1000 and Sun Blade
2000 platforms, Patch 111292 has been withdrawn from Sunsolve. For
all affected platforms, the problem has been corrected in OBP version
4.6.7, which is available with the following patches:
Patch 111292: Sun Blade 1000, Sun Blade 2000, Sun Fire 280R, Netra 20
Patch 112186: Sun Fire V880
Patch 113034: Sun Fire V480
See the special workaround below which may be needed for Sun Blade 1000
and Sun Blade 2000 systems.
IMPLEMENTATION:
---
| | MANDATORY (Fully Proactive)
---
---
| | CONTROLLED PROACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
CORRECTIVE ACTION:
An Authorized Sun Services Field Representative should address the above
mentioned problem by following the recommendation as shown below.
Customers who have installed OBP 4.6.{0-6} on one of the affected
platforms, and are experiencing the system hang, should upgrade to OBP
4.6.7 or a later version using one of the following patches:
Patch 111292 Sun Blade 1000, Sun Blade 2000, Sun Fire 280R, Netra 20
Patch 112186 Sun Fire V880
Patch 113034 Sun Fire V480
Sun Blade 1000 and Sun Blade 2000 customers who have already installed
OBP version 4.6.6 and who are experiencing the system hang will need
to take extra steps to be able to boot to Solaris in order to perform
the upgrade. Possible solutions include:
1. Physically remove CPU1 in order to boot to Solaris as a single
CPU system. After the OBP upgrade is finished, this second CPU may
be re-installed.
OR
2. Temporarily boot a different device containing an earlier version of
Solaris. After the OBP upgrade is complete, the system may be
booted to the original Solaris version.
OR
3. Temporarily disable the secondary CPU from the eeprom via OBP so
that it is possible to boot to Solaris as a single CPU system.
Then install the OBP patch. The steps are:
a. Identify the secondary CPU.
ok show-devs
/pci@8,600000
/pci@8,700000
/memory-controller@1,400000
/SUNW,UltraSPARC-III@1,0 <----- Secondary CPU
/memory-controller@0,400000
/SUNW,UltraSPARC-III@0,0 <----- Primary CPU
b. Disable the secondary CPU:
ok " /SUNW,UltraSPARC-III@1,0" $delete-device
c. The system can now be booted as a single CPU system:
ok boot
d. Install the OBP patch.
e. The secondary CPU will automatically be re-enabled the next
time the system is power-cycled.
COMMENTS:
None
--------------------------------------------------------------------------
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.Central/
* From there, select the appropriate link to browse the FIN or FCO index.
Internet Access:
_______________
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
________
Send questions or comments to finfco-manager@Sun.COM
--------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.