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

FIN #: I1051-1

Status: active

Synopsis: Sun Fire V100 boot issues with dmfe(7D) 2.0 ethernet driver.

Create date: Dec/19/03

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Sun Fire V100, Netra X1

Product Category: Software / Solaris

Product Affected: 

Systems Affected:
-----------------  
Mkt_ID   Platform   Model   Description           Serial Number
------   --------   -----   -----------           -------------
  -       N19        All    Sun Fire V100              -  
  -       N19        All    Netra X1                   -


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

Parts Affected: 

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

References: 

BugID: 4844765 , 4920103 
Patch: 112168-03 , 114388-03 
ESC:   548176

Problem Description: 

Sun Fire V100 and Netra X1 Servers may not boot or may boot very slowly in 
specific instances if version 2.0 of the dmfe(7D) ethernet driver is installed.

This issue could affect any Sun Fire V100 or Netra X1 Server running Solaris 8 
or higher, with version 2.0 of the dmfe driver, under one of the following 
conditions:

1. The system is set up with both network interfaces (dmfe0 and dmfe1) 
   configured and both network cables are removed prior to booting the
   system (i.e., the links are down).

   
  In this case, the system hangs after displaying the Solaris banner while 
  booting from the hard disk.



  In order to check if the system is configured with both network interfaces, 
  run `ls -l /etc | grep hostname` from the command line.  The output should 
  look something like this:



  # ls -l | grep hostname

  -rw-r--r--   1 root     root           7 Nov  6 15:58 hostname.dmfe0     

  -rw-r--r--   1 root     other          7 Nov  6 15:59 hostname.dmfe1 


2. The system is booted from CDROM with at least one of the network interfaces 
   set up and the ethernet cable is removed.
  In this case, the system takes
   an exceptionally long time (several hours) to boot from CDROM.  This case
   will not apply to the Netra X1 since it has no CDROM.
   
To determine if version 2.0 of the dmfe driver is installed and running,
use the modinfo(1M) command.

   # modinfo | grep dmfe
   70 102ffa0f   513c 231   1  dmfe (Davicom DM9102 v2.0)
   
This issue occurs due to bug 4844765  in dmfe driver version 2.0, where the 
delay routine gets called in software interrupt context in the dmfe driver 
when the link goes down.
   
This issue is addressed by dmfe patches for Solaris 8 and 9.

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.

Upgrade to the latest dmfe patch:


   112168-03  or later for Solaris 8
   114388-03  or later for Solaris 9



If the following (unpatched) Solaris releases are booted from CDROM, make sure 
to have at least one of the dmfe interfaces connected to the network.



   Solaris 8 HW 7/03 

   Solaris 9 HW 8/03

   Solaris 9 HW 4/03

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/index.html

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

Status: active