___________________________________________________________________

***  Sun Confidential:  Internal Use and Authorized VARs Only  ***
__________________________________________________________________

This message including any attachments is confidential information
of Sun Microsystems, Inc.  Disclosure, copying or distribution is
prohibited without permission of Sun.  If you are not the intended
recipient, please reply to the sender and then delete this message.
__________________________________________________________________

			FIELD CHANGE ORDER
          (For Authorized Distribution by Enterprise Services)
          

FCO #: A0246-1

Status: inactive

Date: Nov/05/2004

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Sun Fire 12K, Sun Fire 15K

Product Category: Server / System Component

Product Affected: 

Systems Affected:

Mkt_ID   Platform   Model    Description        
------   --------   -----    -----------      
  -	  F15K	     -       Sun Fire 15K	
  -	  F12K	     -       Sun Fire 12K	



X-Options Affected:

Mkt_ID      Platform    Model    Description       
------      --------    -----    -----------	
X4575A      F12K	-	 hsPCI I/O Board w/ 5.0v PCI Cassette

Parts Affected: 

Part Number	           Description             	     
-----------	           -----------	
501-5600-08 (Or Less)	   5.0V hsPCI Cassette

References: 

ECO:	WO_26575	
   LEAP: 2377	
   BugID: 4830665

Issue Description: 

A Crystal-2A card (or other PCI adapter cards) in Slot 1 of the hsPCI I/O Board
which uses a 5.0v PCI cassette may not be recognized upon boot or may unexpectedly fail
to initialize.  This issue causes devices attached to the Crystal-2A (or other PCI
adapter cards) to lose availability.

There is also a potential for the loss of previously configured NVRAM settings on
the Crystal2A which would cause it to revert back to the default NVRAM settings.

The affected configuration is the following:

   - hsPCI I/O Board with a 5.0v PCI Cassette in Slot 1

Note:  The issue has been only been observed with the Crystal-2A PCI Dual FC
Network Adapter, however it is believed that other adapter cards might also be
affected.  Exactly what other cards might be affected is not known.


Symptoms
--------

The symptoms of this issue are improper initialization of devices and lack
of recognition of devices upon boot up.

It is unpredictable.  On occasion some initializations and/or boot sequences
will work but on other occasions initializations and boot up will fail.

Possible error messages would include:

   Mar 11 ... [ID 702911 user.error] RECONFIGURING IO7S1
   Mar 11 ... pcihp: [ID 709949 kern.notice] NOTICE: pcihp (pcisch2): 
              card is inserted in the slot e07b1slot1 (pci dev 1)
   Mar 11 ... [ID 398841 kern.notice] NOTICE: vca1: Timed out
              waiting for POST, attempting to reset device.
   Mar 11 ... [ID 586887 kern.notice] NOTICE: vca1: Resetting board...
   Mar 11 ... [ID 725567 kern.warning] WARNING: vca1: Timeout
              waiting for POST.  Device hung?
   Mar 11 ... [ID 618048 kern.warning] WARNING: vca1: Unable to initialize device!
   Mar 11 ... pcihp: [ID 250731 kern.warning] WARNING: pcihp 
              (pcisch2): failed to attach one or more drivers for the card
              in the slot e07b1slot1

If using the cfgadm(1M) command, output would show:

   pcisch2:e07b1slot1  disconnected  unconfigured  unknown  C5V0


Final determination of this issue can be made by moving the cassette with
the Crystal-2A card from Slot 1 to Slot 3. If the devices are now recognized
and initialized properly when in Slot 3 then this issue has been encountered.


Root Cause
----------

This issue was root caused to a grounding defect with Slot 1 of the hsPCI I/O
Board.  However, it was decided to address the grounding by modifying the 5.0v
cassette.

Slot 1 on the hsPCI I/O Board does not does not follow the PCI Bus specification.
The hsPCI slot 1 is fixed at 5 volts and 33Mhz.  The PCI Bus specification section
7.5.1 states "Expansion boards and bus segments not capable of operation in 66Mhz
mode must connect the M66EN pin to ground.".  This pin is not connected to ground
in this slot on the hsPCI board as it should be, but since the 5.0v cassette is
only used on 33Mhz segments, the 5.0v cassette has been modified to ground this pin
as a solution to the hsPCI board defect.

The 501-5600-09 (or above) addresses the issue by removing a capacitor
on the 5.0v cassette and replacing it with a resistor to tie the required
signal to ground.


Corrective action was made available by Sun manfacturing via ECO# WO_26575
released September 9, 2003.

Corrective action was made available by Sun Services via LEAP# 2377
released September 11, 2003.

Implementation: 

---
|   |   MANDATORY (Fully Pro-Active)
 ---

 ---
|   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
 ---

 ---
| X |   UPON FAILURE
 ---

Replacement Time Estimate: 

0.25 hours

Special Considerations: 

This FCO will have a timezone phased release based on material
readiness as follows:

   All Americas    Nov 05, 2004
   EMEA            Nov 15, 2004
   APAC/Japan      Nov 30, 2004

The above dates represent when each timezone has determined
they will be materially ready to support this FCO.

Corrective Action: 

If this issue is encountered, upon failure replace the following:

   - replace 501-5600-08 (or lower) with 501-5600-09 (or above)
	

Note: Procedures for replacement can be found in Chapter 9 of:

   http://sunsolve2.central.sun.com/data/806/806-3512/pdf/806-3512-12.pdf

Comments: 

None.



________________________________________________________________________

NOTE: FCO Tracking Instructions for Radiance/SPWeb:
--------------------------------------------------

If a Radiance case involves the application of an FCO to solve a customer
issue, please complete the following steps in Radiance/SPWeb prior to
closing the case:
 
    o Select "Field Change Order" in the REFERENCE TYPE field.

    o Enter FCO ID number in the REFERENCE ID field.
      For example; A0222-1.

If possible, include additional details in the REFERENCE SUMMARY field
(ie. Upgrade complete, customer declined, etc.)
________________________________________________________________________

Implementation Notes
--------------------

In case of "Mandatory" FCOs, Sun Services will attempt to contact
all known customers to recommend proactive implementation.

For "Controlled Proactive" FCOs, Sun Services mission critical
support teams will initiate proactive implementation efforts for
their respective accounts, as required.

For "Upon Failure" FCOs, Sun Services and partners will implement
the necessary corrective actions as the need arises.

The CIC process must be used for proactive hardware replacement
requests when an FCO is classified as "Upon Failure".


Billing Information
-------------------

Warranty: Sun will provide parts at no charge under Warranty
          Service.  On-Site Labor Rates are based on specified
          Warranty deliverables for the affected product.

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.

________________________________________________________________________

All FCO documents are accessible via Internal SunSolve.  Type "sunsolve"
in a browser and follow the prompts to Search Collections.

For questions on this document, please email:

        [email protected]

The FIN and FCO homepage is available at:

        http://sdpsweb.central/FIN_FCO/index.html

For more information on how to submit a FCO, go to:

        http://pronto.central/fco.html

To access the Service Partner Exchange, use:

        https://spe.sun.com

________________________________________________________________________