Document Audience: | INTERNAL |
Document ID: | I0973-1 |
Title: | Sun Blade 1000/2000 systems may fail to boot from disk or may boot as a Sun Fire 280R due to an OBP firmware bug. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2003-05-22 |
---------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I0973-1
Synopsis: Sun Blade 1000/2000 systems may fail to boot from disk or may boot as a Sun Fire 280R due to an OBP firmware bug.Create Date: May/21/03
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Sun Blade 1000/2000
Product Category: Desktop / Service
Product Affected:
Systems Affected:
-----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- A28 ALL Sun Blade 1000 -
- A29 ALL Sun Blade 2000 -
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- - - - -
Parts Affected:
Part Number Description Model
----------- ----------- -----
- - -
References:
BugId: 4822930 - Sun Blade 1000 powers up as Sun-Fire 280R for some
rev. BBCs.
PatchId: 111292-12: Sun Blade 1000, Sun Fire 280R and Netra[tm] T20
Blade 2000.
ECO: WO_26077
Issue Description:
Sun Blade 1000/2000 systems may fail to boot from disk or may boot
as a Sun Fire 280R due to an Open Boot PROM (OBP) issue.
This issue is most prevalent in systems shipped during January 2003,
but could occur in any Sun Blade 1000/2000 system with OBP version
less than 4.5.21. To determine a system's OBP version, run one of
the following:
.version (from the OBP "ok" prompt)
/usr/sbin/prtconf -V (from a Solaris prompt)
When this issue occurs there are two possible scenarios:
1. A Sun Blade 1000/2000 system tries to boot as a Sun Fire 280R
but fails to find the boot disk. The following messages may
be displayed:
"Could not read keyswitch position!"
"Could not find boot device"
"Could not read fan or power supply status"
When the system tries to come up as a Sun Fire 280R, it will not
see any disks because the physical address of the boot device is
different for a Sun Fire 280R versus a Sun Blade 1000/2000.
2. The Sun Blade 1000/2000 boots as a Sun Fire 280R. This would
only happen when the system boots over the net. This is not
desirable due to differing thermal parameters and software
operating environment.
A bug in the OBP firmware does not take into consideration a corner
case for the BBC Scratch RAM where the OBP determines what kind of
system the common Sun Blade 1000/2000/Sun Fire 280R System Board is
installed in.
The bug is an OBP dependency on an uninitialized register value within
the motherboard BBC chip. Recent batches of BBC chips have been coming
in with a different uninitialized signature and results in a Sun Blade
1000/2000 system being identified as a Sun Fire 280R. Subsequent queries
for a Sun Fire 280R system attributes such as a keyswitch and RSC card
will then fail and the "disk" boot device cannot be recognized.
This issue has been addressed with the release of OBP firmware version
4.5.21, made available in Manufacturing via ECO WO_26077. This firmware
version is available as patch 111292-12.
Implementation:
---
| | MANDATORY (Fully Proactive)
---
---
| | CONTROLLED PROACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
The following recommendation is provided as a guideline for authorized
Sun Services Field Representatives who may encounter the above
mentioned issue.
Install OBP patch 112292-12 or later on Sun Blade 1000/2000 systems
having OBP versions less than 4.5.21. Please follow the special firmware
installation instructions provided with the patch README file.
If a system will not boot to allow patch installation, run the following
from the OBP "ok" prompt:
ok setenv diag-switch? true
ok reset
This permits the system to boot normally.
Comments:
None
============================================================================
Implementation Footnote:
i) In case of MANDATORY FINs, Sun Services will attempt to contact
all affected customers to recommend implementation of the FIN.
ii) For CONTROLLED PROACTIVE FINs, Sun 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, Sun 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.central/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 index.
Internet Access:
----------------
* Access the top level URL of https://spe.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------