Asset ID:	1-72-1010901.1
Update Date:	2012-07-30
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1010901.1 :   Installation of Solaris[TM] 9 04/04 or Solaris[TM] 10 causes domain to panic or ERROR Fast Data Access MMU Miss  


PreviouslyPublishedAs
215041

Applies to:

Sun Netra 1280 Server
Sun Fire V1280 Server
Sun Fire 3800 Server
Sun Fire 4800 Server
Sun Fire 4810 Server
All Platforms
***Checked for relevance on 19-DEC-2011***

Symptoms

System panics with a Fast Data Access MMU Miss error when trying to install Solaris[TM] 9 or 10.

The following issue has been reported when trying to install Solaris[TM] 9 04/04 or Solaris[TM] 10 on a Sun Fire[TM] v1280, E2900, 3800, 4800, 4810, 6800, E4900, E6900 or netra 1280, 1290 domain from cdrom or network.

Basically the system panics with the message, "Fast Data Access MMU Miss".

Actual error output (from console logs):

Rebooting with command: boot cdrom
Boot path: /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@6,0:f Boot args:
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Redirected to slice: 1
Loading: /platform/SUNW,Sun-Fire/ufsboot
Loading: /platform/sun4u/ufsboot
ERROR: Fast Data Access MMU Miss
debugger entered.
>ok

The issue has also been seeing when doing a "boot net install". Sometimes it panics with following message:

panic[cpu8]/thread=140a000: BAD TRAP: type=31 rp=1409430 addr=7000007dff8 mmu_fsr=0

Changes

{CHANGE}

Cause

{CAUSE}

Solution

Validate that the System Controller Firmware has been updated prior to the Solaris upgrade.

If you have a domain that has encountered this issue, it could be the result of an incompatibility with the version of ScApp installed on the System Controller (SC).

You may notice that an earlier Solaris version, such as Solaris[TM] 8 02/02, boots fine from cdrom.

In the Solaris 9 4/04 Sun Hardware Platform Guide, Chapter 1 (the Solaris documentation is available here :- http://docs.oracle.com/cd/E19683-01/index.html  )    it states:

    To install the Solaris 9 4/04 operating environment on specific Sun Fire and Netratrademark servers, you must first update the firmware on the server. If you do not update the firmware before you install the Solaris 9 4/04 software, the server panics. This problem affects the following servers:
       * Sun Fire 3800 server
       * Sun Fire 4800 server
       * Sun Fire 4810 server
       * Sun Fire 6800 server
       * Sun Fire V1280 server
       * Netra 1280 server

    If this problem occurs, the following error message is displayed:

    panic[cpu0]/thread=140a000: BAD TRAP: type=34 rp=147e9e0 addr=5586ee326973add3 mmu_fsr=0

    The ok prompt is displayed.

    Workaround:

    For Sun Fire 3800, 4800, 4810, or 6800 servers, apply the most current version of the firmware patches available, for example, firmware update 5.15.4 or 5.15.3.

    For Sun Fire V1280 or Netra servers, apply the most current version of the firmware patch available

That chapter describes version 5.13.x as the most recent version of the firmware.  In fact, the most recent version of firmware is now 5.20.x and this version will continue to be maintained via Patch ID 114527

So, to avoid the panic behavior described within this document if upgrading to Solaris 9 or 10, make sure the ScApp version is upgraded prior to the Solaris OS installation.


Product
Sun Fire V1280 Server
Sun Fire 6800 Server
Sun Fire 3800 Server
Sun Fire 4810 Server
Sun Fire 4800 Server
Sun Fire E2900 Server
Sun Fire E4900 Server
Sun Fire E6900 Server
Netra 1280 Server
Netra 1290 Server

Fast Data Access MMU Miss, panic, boot cdrom, bad trap, install, solaris, sun fire, sunfire, serengeti, lw8, debugger entered, scapp, SC, firmware
Previously Published As
79415


Attachments

This solution has no attachment