Document Audience: | INTERNAL |
Document ID: | I1098-1 |
Title: | System may fail self-test with "OBP (Open Boot PROM) not responding" on Sun Fire V440 and Netra 440. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2004-11-23 |
------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
------------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I1098-1
Synopsis: System may fail self-test with "OBP (Open Boot PROM) not responding" on Sun Fire V440 and Netra 440.Create Date: Jun/08/04
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Sun Fire V440, Netra 440
Product Category: Server / Diag-Doc-Service
Product Affected:
Systems Affected:
-----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- N42 ALL Netra 440 -
- A42 ALL Sun Fire V440 -
X-Options Affected:
-------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
X7415A - - XOPT 1.062GHz 2GB DDR1 SFV440 -
X7416A - - XOPT 1.28GHz 4GB DDR1 SFV440 -
Parts Affected:
Part Number Description Model
----------- ----------- -----
501-6369-03 ASSY A42 1.064GHz 0MB CPU BD -
501-6370-04 ASSY A42 1.280GHz 0MB CPU BD -
References:
N/A
Issue Description:
The intent of this FIN is to inform the field of a known issue which
exists when a CPU module may not be fully seated into a system board
on Sun Fire V440 or Netra 440 platforms. As a result of this issue,
the field may unnecessarily replace CPU modules that only need
to be reseated.
When Power-On is performed without the CPU module fully seated, and
running the POST test, intermittent error messages will be displayed on
the console screen which prevents the system from passing self-test.
Though the cause of this failure is still under investigation, the
solution is normally resolved by reseating the CPU module(s).
Below are examples of possible symptoms/messages if the CPU module is
not fully seated on the system board;
Example #1:
sc> console
Enter #. to return to ALOM.
SC Alert: Host Power-On Failed: System Power OK, Open Boot not
responding
...
Comment: Reseat CPU sequencially (or all at once) until failure
is removed.
Example #2:
sc> console
Enter #. to return to ALOM.
CPU 0000.0000.0000.0002 AFSR 0082.0000.030b.0000 JEIC ISAP
AFAR 0000.0000.0000.0000
CPU 0000.0000.0000.0001 AFSR 0082.0000.030b.0000 JEIC ISAP
AFAR 0000.0000.0000.0000
CPU 0000.0000.0000.0000 AFSR 0082.0000.030b.0000 JEIC ISAP
AFAR 0000.0000.0000.0000
SC Alert: Host Power-On Failed: System Power OK, Open Boot not
responding
.....
Comment: In this example, reseating CPU3 would normally remove
the failure.
Example #3:
sc> console
Enter #. to return to ALOM.
SC Alert: Host Power-On Failed: System Power OK, Open Boot not
responding
@(#)OBP 4.10.10 2003/08/29 06:25 Sun Fire V440
Clearing TLBs
Power-On Reset
Executing Power On SelfTest
@(#) Sun Fire[TM] V440 POST 4.10.9 2003/08/05 13:15
/export/common-source/firmware_re/post/post-build-4.10.9/Fiesta/ <---
--->chalupa/integrated (firmware_re)
0>Hard Powerup RST thru SW0>CPUs present in system: 0 1 2 3
0>OBP->POST Call with %o0=00000000.01114000.
0>Diag level set to MAX.
0>MFG mode set to AFT CPU
0>I/O port set to TTYA.
0>
0>Start selftest...
0>Waiting for CPU2, timeout in 37 seconds.
3>Waiting for master CPU=0, timeout in 14 seconds...
1>Waiting for master CPU=0, timeout in 14 seconds...
0>Waiting for CPU2, timeout in 24 seconds.
0>Waiting for CPU2, timeout in 12 seconds.
0>
0>ERROR: TEST = Power on Reset Initialization
0>H/W under test = Motherboard, CPU (system initialization)
0>Repair Instructions: Replace items in order listed by 'H/W under
test' above
0>MSG = ERROR: Slave timeout waiting for 2 to finish, offlining cpu!
0>END_ERROR
1>Waiting for master CPU=0, timeout in 9 seconds...
Comments: Reseating CPU 2 normally correct this error.
Unknown - still under investigation
Engineering is currently investigating this issue. This FIN will be updated
once root cause has been determined..
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.
In most cases, reseating the CPU module(s) has been successful in
resolving this issue. If, after reseating the CPU module(s), the
system continues to fail self-test, reseat the CPU module(s) a second
time. If the system still does not pass self-test, contact PTS for
further instructions.
A small number of cases have been reported to have resolved this issue
by reseating the CPU module(s) a second time.
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:
SunSolve Internal 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://spe.sun.com
FIN/FCO Homepage Access:
_________________________
* Access the top level URL of http://sdpsweb.Central/FIN_FCO/index.html
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
To submit either a FIN or FCO refer to the following URLs for templates
and instructions;
* For FCO: http://pronto.central/fco.html
* For FIN: http://pronto.central/fin.html
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------