---------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                            FIELD INFORMATION NOTICE
                  (For Authorized Distribution by Sun Services)

FIN #: I1016-1                              Date: May/26/04

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Sun Fire V480

Product Category: Server / System Component

Product Affected: 

Systems Affected:
----------------
  
Mkt_ID   Platform    Model   Description     Serial Number
------   --------    -----   -----------     -------------
  -       A37         ALL    Sun Fire V480          -

X-Options Affected:
-------------------
Mkt_ID     Platform     Model     Description         Serial Number
------     --------     -----     -----------         -------------
  -           -           -            -                    -

Parts Affected: 

--------------------- 
Part Number   Description       Model
-----------   -----------       -----
  -              -                -

References: 

BugId: 4898531  "FATAL RESET from DAR/DCS/CDX" under heavy I/O load
ESC: 545325, 547384, 547500

Issue Description: 

CHANGE HISTORY
   ==============
  
   Date Modified: May/26/04
   Update: This FIN becomes OBSOLETE due to the release of FCO A0226-1.
  

In an extremely limited number of applications, and with a single system 
configuration, the Sun Fire V480 system may experience a fatal reset and 
reboot with the following error message:

   ERROR: System "FATAL RESET" from DAR/DCS/CDX.
 
The specific configuration which triggers this situation is as follows:

 A) High data activity occurring to or from a PCI card installed in one of 
    the 66MHz PCI slots (PCI slot 0 or 1).
    
 B) Some or all of the data being transferred is transported via the second 
    onboard ethernet interface "ce1" (Cassini ASIC).  If a Cassini PCI
    ethernet card is also installed (P/N 501-5524, or 501-5902) then the 
    onboard controller number may be different due to the PCI probe order.  
    
    Both A) and B) must be true for this error state to occur.
    
This issue could occur when high activity on the PCI-A and PCI-C busses in 
the area of CE1 generates a glitch on a Safari bus control line, creating a 
parity error.  The error condition that causes this situation is extremely rare 
and is configuration specific.

When this issue occurs, the system will reset.  After the reset, the system 
reboots and the message "FATAL RESET from DAR/DCS/CDX" will appear on the 
system console.  No core files are generated and the fatal reset output does 
not get logged to the /var/adm/messages file.

There is currently no permanent resolution.  Customer sites experiencing this 
issue should use the workaround procedures provided below. 

***************************************************************************

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.

A long-term corrective action plan is being developed by Sun and will be 
delivered via Sun's Service team.   In the meantime, utilize the following
workarounds.

The existing workarounds require some configuration changes:
 
a) Use only the ce0 onboard network interface.  The ce1 onboard 
   interface should not be used (should be disabled via ifconfig(1M)) and, 
   if necessary, a second network interface card can be installed.
   
   OR

b) If possible and acceptable for the customer, cards should be moved 
   from 66MHz PCI slots to 33MHz slots (PCI slots 2,3,4,5). 

Any system configuration which can be used according to a) and b) which 
avoids the configuration described in the Problem Description will prevent 
the issue from occurring.

*************************************************************************

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 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
--------------------------------------------------------------------------