440MHz/450MHz Modules for Ultra 60/80, Enterprise 220R/420R and Netra t Platforms may Experience Early Life Failures |
|
| Category : | Availability |
| Release Phase : | Resolved |
| Product : | Sun Enterprise 220R Server Sun Enterprise 420R Server Ultra 60 Workstation Ultra 80 Workstation
|
| Bug Id : | None
|
| Date of Workaround Release : | 16-JAN-2003
|
| Date of Resolved Release : | 28-FEB-2003
|
Impact
440MHz and 450MHz UltraSPARC II Modules in Ultra 60/80, Enterprise 220R/420R and Netra t platforms may experience early life failures resulting in possible panics, hard hangs or resets.
The probability of experiencing the described issue is extremely low.
Contributing Factors
This issue can occur with the following configurations :
SPARC
-
440MHz UltraSPARC II Modules
-
450MHz UltraSPARC II Modules
CPU Module Part Number: 501-6058-02 (or earlier) :
System Serial Numbers
-------------- -------------------
Ultra 60 144xxxxx - 246xxxxx
Ultra 80 144xxxxx - 246xxxxx
Enterprise 220R 144xxxxx - 246xxxxx
CPU Module Part Number: 501-6071-01:
System Serial Numbers
-------------- -------------------
Ultra 60 144xxxxx - 246xxxxx
Ultra 80 144xxxxx - 246xxxxx
Enterprise 220R 144xxxxx - 246xxxxx
Enterprise 420R 144xxxxx - 246xxxxx
CPU Module Part Number: 501-6209-02 or earlier (* see New Note below):
System Serial Numbers
-------------- -------------------
Netra t 1405 144xxxxx - 246xxxxx
Netra t 1400 144xxxxx - 246xxxxx
Netra t 1120 144xxxxx - 246xxxxx
Netra t 1125 144xxxxx - 246xxxxx
CPU Module Part Number: 501-5682-03:
System Serial Numbers
-------------- -------------------
Netra t 1405 220xxxxx - 319xxxxx
Netra t 1400 220xxxxx - 319xxxxx
Netra t 1120 220xxxxx - 319xxxxx
Netra t 1125 220xxxxx - 319xxxxx
For Serial Numbers: 144xxxxx - 246xxxxx:
Systems manufacted between November 2001 and November 2002 may contain potentially affected CPU modules. The affected system serial number range is 144XXXXX through 246XXXXX. (the first 3 digits reflect the year and week of manufacture).
Locate the CPU module part number. If it is 501-6071-01, 501-6209-01, or 501-6058-02 (or earlier) and without a "DPCO 336" sticker, the system is possibly affected by the described issue.
If the system serial number is outside of this range, it will not have the affected modules that are listed above unless the module has been replaced.
For Serial Numbers: 220xxxxx - 319xxxxx:
Systems manufacted between May 2002 and May 2003 may contain potentially affected CPU modules. The affected system serial number range is 220XXXXX through 319XXXXX. (the first 3 digits reflect the year and week of manufacture).
For CPU module part number 501-5682-03, please locate the CPU module serial number. If it is 103XXX and above, it may be affected. To find the CPU module serial number, look at the barcoded label on the CPU module. There will be a number above it, example 5015682106778. The last 6 digits (106778 in this case) is the serial number. In this example, 106778 is greater than 103XXX and therefore possibly affected.
* New Note 05-Mar-2004:
Additional Information For Serial Numbers: 144xxxxx - 246xxxxx:
Locate the CPU module part number. If it is 501-6071-01 or 501-6058-02 (or earlier) and without a "DPCO 336" sticker, the system is possibly affected by the described issue. If the system serial number is outside of this range, it will not have the affected modules that are listed above unless the module has been replaced.
If it is 501-6209-02 (or earlier), please locate the CPU module serial number. If it is 0 through 1000 or 2000 through 3500, it may be affected. If it is 1001-1999, or greater than 3500, it will not be affected. To find the CPU module serial number, look at the barcoded label on the CPU module. There will be a number above it, example 50162091300. The last 4 digits (1300 in this case) is the serial number. In this example, 1300 is within the range of modules that are not affected.
Symptoms
The system may experience a panic, hard hang, or reset. These symptoms are generic and could indicate other issues not covered by the described issue in this document.
Workaround
Because this issue manifests itself as a common system failure, consultation with your Sun Services representative is necessary before replacing hardware.
Resolution
This issue is addressed with the implementation of a Field Change Order (FCO).
Please contact your local Sun Services Representative and reference this document for determining the appropriate Field Change Order (FCO).
Modification HistoryDate: 28-FEB-2003
-
State: Resolved (and Closed)
-
Updated Resolution section
Date: 10-APR-2003
-
Updated Contributing Factors
Date: 14-APR-2003
-
Updated Contributing Factors
Date: 15-APR-2003
-
Updated Contributing Factors
Date: 05-MAY-2003
-
Updated Contributing Factors
Date: 05-MAR-2004
-
Added new information on part 501-6209-02 to Contributing Factors
AttachmentsThis solution has no attachment