Document Audience: | INTERNAL |
Document ID: | A0195-1 |
Title: | Ultra Enterprise 6500 systems are susceptible to noise conditions that can trigger a Fatal Reset Error. |
Copyright Notice: | Copyright © 2007 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | Fri Mar 28 00:00:00 MST 2003 |
----------------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
----------------------------------------------------------------------------
FIELD CHANGE ORDER
(For Authorized Distribution by Enterprise Services)
FCO #: A0195-1
Status: inactive
Synopsis: Ultra Enterprise 6500 systems are susceptible to noise conditions that can trigger a Fatal Reset Error.Date: Mar/28/2003
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Ultra Enterprise 6500
Product Category: Server / System Component
Product Affected:
Systems Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- E6500 ALL Ultra Enterprise 6500 -
X-Options Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
x2602A E6x00 - CPU/Memory Board xoption -
Parts Affected:
Part Number Description Model
----------- ----------- -----
501-4882-08(Or Less) CPU/Memory Board - E6x00 -
References:
LEAP: 2183
LEAP: 2140
BugID: 4467248
BugID: 4358991
BugID: 4707170
ECO: WO_25777
ECO: WO_25216
URL: Best Practices http://bestpractices.central/
Issue Description:
Ultra Enterprise 6500 servers may experience a Fatal Reset due to trace
noise on the system board in specific configurations.
Failing configurations tend to include the 464MHz CPU Modules. The higher
the frequency of the CPU modules the larger the cumulative noise becomes
on the VDDcore_0 and VDDcore_1 traces. This noise when combined with DIMM
noise exceeds the signal threshold level which causes the FATAL RESET.
Fatal Reset errors can been seen on any system and can be caused by many
things, but this particular cause of fatal reset has only been reported
on the E6500 with full up processors with speeds at or above 464MHz, and
with heavily utilized memory. The reported error typically shows as
"fatal error FATAL".
A limited number of Ultra Enterprise 6500 servers shipped between
April 30, 1998 and November 15, 2001 are affected. The expected failure
rate of these systems related to this issue is one percent. Any E6500
server with CPU/Memory board 501-4882-08 (or below) installed may be
susceptible to this situation. This problem has not been reported on
other CPU/Memory board part numbers, or on system types other than
the E6500.
Root cause determined the affected system board with higher speed modules
(464MHz or higher), and with heavily utilized memory was exceeding the
noise threshold on the VDDcore_0 and VDDcore_1 signals and causing a
Fatal Reset.
Initially, corrective action was implemented in Manufacturing by changing
the components at locations U2301 and U2414 from AD708T to AD708S, which
have better noise margin. These changes were documented and made available
in manufacturing via ECO# WO_22316 by dash rolling the CPU/Memory board
from 501-4882-07 to -08 as of December 11, 2001. However these changes
were actually cut into manufacturing as of November 16, 2001. These
corrective actions were made available in Sun Services via LEAP# 1885 as
of December 19, 2001.
Additional corrective action was implemented in Manufacturing by adding
1000pF capacitors between R2426 and R2427, and between R2513 and R2514.
Additionally 1.01uF capacitors were added between pins 3 and 4 of U2414
and U2301. These changes were documented and made available within
manufacturing via ECO# WO_25216 by dash rolling the CPU/Memory board from
501-4882-08 to -09 as of November 18, 2002. Corrective action was made
available in Sun Services via LEAP# 2140 as of November 18, 2002.
Later it was determined that ECO that dash rolled the boards to -09
had incorrect rework instructions. However all boards reworked to
-09 were correctly done. Therefore, all -09 boards are equivalent
to -10 boards. Although these -09 boards will function properly
ECO# WO_25777 was written on January 29, 2003 to make the -10
available, and LEAP# 2183 was released on February 3, 2003 to
rework all -09 boards to -10 upon return.
Parts Affected:
End of Service Life (EOSL)
Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | UPON FAILURE
---
Replacement Time Estimate:
1.0 hours
Special Considerations:
Replacements should only occur after attempting to eliminate
this error via the Best Practices website mentioned below, and
then only for those boards that have failed. Proactive
replacements are not authorized.
Corrective Action:
Fatal Resets can be caused by many things. Other Fatal Reset fixes should
be pursued before changing out System boards. Reference the Best Practices
web site at;
http://bestpractices.central/
If corrective actions per the Best Practices web site are unsuccessful
in eliminating this error condition, upon failure replace 501-4882-08
(or below) with 501-4882-09 (or above).
Comments:
Billing Type:
Warranty: Sun will provide parts at no charge under Warranty
Service. On-Site Labor Rates are based on how the
system was initially installed.
Contract: Sun will provide parts at no charge. On-Site Labor Rates
are based on the type of service contract.
Non Contract: Sun will provide parts at no charge. Installation by
Sun is available based on the On-Site Labor Rates
defined in the Price List.
--------------------------------------------------------------------------
Implementation Footnote:
________________________
i) In case of Mandatory FCOs, Sun Services will attempt to contact
all known customers to recommend the part upgrade.
ii) For controlled proactive swap FCOs, Sun Services mission critical
support teams will initiate proactive swap efforts for their respective
accounts, as required.
iii) For Replace upon Failure FCOs, Sun Services partners will implement
the necessary corrective actions as and when they are required.
--------------------------------------------------------------------------
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 or FCO index.
Internet Access:
_______________
* Access the top level URL of https://spe.sun.com
--------------------------------------------------------------------------
General:
________
Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------