Fujitsu SPARC Enterprise M3000 Product Notes page 63

Oracle Solaris OS Issues and Workarounds for All Supported Releases (Continued)
TABLE 3-4
M4000
CR ID M3000 M4000
6660168 O O
6745410 O O
M8000
M9000 Description
O If a ubc.piowbeue-cpu error occurs
on a domain, the Oracle Solaris Fault
Management cpumem-diagnosis
module might fail, causing an
interruption in FMA service.
If this happens, you will see the
following output in the console log:
SUNW-MSG-ID: FMD-8000-2K,
TYPE: Defect, VER: 1,
SEVERITY: Minor
EVENT-TIME: Fri Apr 4 21:41:57
PDT 2008
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. Refer to
http://sun.com/msg/FMD-8000-2K
for more information.
AUTO-RESPONSE: The module has
been disabled. Events destined
for the module 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. Use fmadm reset
<module> to reset the module.
O Boot program ignores the Kadb option
which causes the system not to boot.
Workaround
If FMA service fails, issue the following
command on the domain to recover:
# svcadm clear fmd
Then restart cpumem-diagnosis:
# fmadm restart cpumem-
diagnosis
Use kmdb instead of kadb.
Chapter 3 Information About Software 49