SRDB ID   Synopsis   Date
20149   Panic or Fast Data Access MMU Miss on 2.5.1 or 2.6 installs on E3000 - E6000 or E3500 - E6500 Servers with 400MHz/8MB cache CPU modules   18 Sep 2001

Status Issued

Description
When trying to install Solaris 2.5.1 HW 11/97 or 2.6 HW 3/98 on a E3000 - E6000
or E3500 - E6500 server with a 400MHz/8MB cache CPU module, booting from cdrom 
or network install server produces:

Fast Data Access MMU Miss error or panics with:

mutex_enter: bad mutex.

            
SOLUTION SUMMARY:
NOTE: This procedure requires downloading and applying patches, so the install
client must have a network connection.

1. Verify OBP version by typing .version at the ok prompt or use the
   /usr/sbin/prtconf -V command at the UNIX prompt.  If needed, upgrade to 
   at least flash PROM version 3.2.21 using patch 103346-25 or greater.

2. ok setenv auto-boot? false

3. ok setenv diag-level min   (this will reduce the POST recycle time)

4. ok reset 

5. ok limit-ecache-size
	
6. ok boot cdrom  (minimum OS support is 2.5.1 HW 11/97 or 2.6 HW 3/98)
	
7. Install the OS but do not allow auto-reboot!

8. # init 0
	
9. ok reset 
	
10. ok limit-ecache-size
	
11. ok boot
	
12. Once the system boots, install the latest kernel patch.
	
    Solaris 2.5.1 --> 103640 and prtdiag patch 104595-09 (minimum
    Solaris 2.6   --> 105181
    
    One option is via sunsolve.sun.com (ftp or html).
    Place the patches .tar.Z files in a directory which can be
    accessed when booted into singleuser mode (ie. in root dir).      

13. Bring the system into singleuser mode by doing the following:

    # init 0  (this will shutdown the machine).
    ok reset  (will reset the machine).
    ok limit-ecache-size
    ok boot -s  (will boot machine into singleuser mode).

    NOTE: Do not execute init S.  That might not bring the machine
    into a "true" singleuser mode.

    Enter root password.

14. Install patches:
    # mount /tmp  (mounts /tmp as a tmpfs).
    copy or move the patch .tar.Z files into /tmp
    uncompress and untar the patches (in /tmp).
    Install the patches.

15. Reboot.


Notes and troubleshooting issues with limit-ecache-size:


1. This is a transient setting in the Open Boot Prom(OBP).
   Anytime the OBP resets, the value is lost and needs to be re-applied.
   Example:
      ok boot cdrom 
      Resetting ...
   
      ok limit-ecache-size
      ok boot [cdrom disk net] 

2. If the OBP continues to reset after following the above procedure, then
   try a power cycle of the system.  Be sure the keyswitch is not in
   diagnostic mode and that stop-a is not being used to get to the ok prompt.

3. To isolate a posible hardware problem, you can boot from a Solaris 7 cdrom
   as the Solaris 7 kernel supports 8mb cache size. If the boot is successful,
   the hardware is most likely ok. 

4. Once the OS and kernel patch have been successfully installed the 
   limit-ecache-size no longer needs to be used when booting the OS from disk.

5. The limit-ecache-size procedure must be followed whenever a Solaris 
   2.6 HW 3/98 or HW 5/98 or Solaris 2.5.1 HW 11/97 CD-ROM is booted.

6. The limit-ecache-size command also needs to be used when installing 
   from a Network Install Server(JumpStart)
   Example:
      ok limit-ecache-size
      ok boot net - install

7. For details on adding a Kernel patch to JumpStart installation see
SUBMITTER: Mark Bennett

APPLIES TO: Hardware, Operating Systems/Solaris/Solaris 2.x
ATTACHMENTS: 


Copyright (c) 1997-2003 Sun Microsystems, Inc.