Sun Microsystems SPARC Enterprise M8000 Product Notes page 28

Solaris OS Issues and Workarounds for All Supported Releases (4 of 4)
TABLE 5
CR ID Description
6660168 If a ubc.piowbeue-cpu error occurs on a
domain, the Solaris Fault Management
cpumem-diagnosis module might fail, causing
an interruption in FMA service.
If this happens, you will see output similar to
the following sample in the console log:
SUNW-MSG-ID: FMD-8000-2K, TYPE: Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Apr
PLATFORM: SUNW,SPARC-Enterprise, CSN: 2020642002, HOSTNAME: <hostname>
SOURCE: fmd-self-diagnosis, REV: 1.0
EVENT-ID: 6b2e15d7-aa65-6bcc-bcb1-cb03a7dd77e3
DESC: A Solaris Fault Manager component has experienced an error that required
the module to be disabled.
information.
AUTO-RESPONSE: The module has been disabled.
will be saved for manual diagnosis.
IMPACT: Automated diagnosis and response for subsequent events associated with
this module will not occur.
REC-ACTION: Use fmdump -v -u <EVENT-ID> to locate the module.
<module> to reset the module.
6660197 DR might cause the domain to hang if either of
the following conditions exist:
• A domain contains 256 or more CPUs.
• More than 256 memory errors are detected.
6663570 DR operations involving the lowest number
CPU might cause the domain to panic.
6664134 Certain service processor-detected faults are
not reported by the XSCF command fmadm
faulty, nor will such faults be passed along
as an ereport to the domain.
6668237 After DIMMs are replaced, the corresponding
DIMM faults are not cleared on the domain.
6718173 If your domain is running one of the following
versions of Solaris OS, the system might
panic/trap during normal operation:
• Solaris 10 5/08 OS
• An earlier version of Solaris 10 OS with
patch ID 127127-11
14 SPARC Enterprise M8000/M9000 Servers Product Notes for XCP 1071 • July 2008
Workaround
If fmd service fails, issue the following
command on the domain to recover:
# svcadm clear fmd
Then restart cpumem-diagnosis:
# fmadm restart cpumem-diagnosis
4 21:41:57 PDT 2008
Refer to http://sun.com/msg/FMD-8000-2K for more
Follow these steps:
1. Set the following parameter in the system
specification file (/etc/system):
set drmach:drmach_disable_mcopy=1
2. Reboot the domain.
Do not use DR to remove the system board that
hosts the CPU with the lowest CPU ID. Use the
Solaris prtdiag command to identify the CPU
with the lowest CPU ID.
Use the XSCF command showstatus or
fmdump instead.
Use the command fmadm repair fmri|uuid
to record the repair. Then you can use the
command fmadm rotate to clear out any
leftover events.
Set the following parameter in the system
specification file (/etc/system):
set heaplp_use_stlb=0
Then reboot the domain.
Events destined for the module
Use fmadm reset