OpenSolaris

Printable Version Enter a New Search
Bug ID 6678015
Synopsis FMA message is not fully displayed for CPU Cache error
State 10-Fix Delivered (Fix available in build)
Category:Subcategory fma:other
Keywords
Responsible Engineer Sean Ye
Reported Against s10u5_08
Duplicate Of
Introduced In solaris_10
Commit to Fix snv_88
Fixed In snv_88
Release Fixed solaris_nevada(snv_88) , solaris_10u7(s10u7_01) (Bug ID:2163578)
Related Bugs 6712475 , 6720030
Submit Date 20-March-2008
Last Update Date 13-June-2008
Description
FMA should display error messages in full
(Copied from comments.)

ere is the console log at that time.

...

SUNW-MSG-ID: SCF-8007-4D, TYPE: Fault, VER: 1, SEVERITY: Major
VENT-TIME: Thu Mar  6 16:32:40 JST 2008
PLATFORM: SPARC Enterprise M9000, CSN: PA30601006, HOSTNAME: DC3-06-1
SOURCE: sde, REV: 1.16
EVENT-ID: ad7ded7b-7062-4c92-8efe-323a6079b4cf
DESC: A non-fatal uncorrectable error associated with a core on a CPU chip
has
been detected.
 Refer to http://sun.com/msg/SCF-8007-4D for more information.
AUTO-RESPONSE: The domain software will attempt to offline the core on the
CPU chip.
IMPACT: The non-fatal uncorrectable error trap may cause the domain to
panic. If
the domain
does not panic, the domain software will attempt to offline the core on
the CPU
chip.
The core of the CPU chip will be deconfigured after the platform is power
cycled or
after the domain reboots or after a Dynamic Reconfiguration operation is
performed.
REC-ACTION: Schedule a repair action to replace the affected Field
Replaceable
Unit (FRU),
the identity of which can be determined using fmdump -v -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~====> Here

According to SCF.po of U5B8(127127-08), the REC-ACTION messages should be
below.
So, it looks the FMA message (REC-ACTION) is not fully displayed...

...

msgstr "Schedule a repair action to replace the affected Field Replaceable
Unit
(FRU),\nthe identity of which can be det
ermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of
the
knowledge article for additional information.\n"

It looks
buffer size for the FMA message is 1024 bytes, the issue may be caused of
this..

127127-08/sun/usr/src/cmd/fm/modules/common/syslog-msgs/syslog.c
================================================================

   170  /*ARGSUSED*/
   171  static void
   172  syslog_recv(fmd_hdl_t *hdl, fmd_event_t *ep, nvlist_t *nvl, const
char
*class)
   173  {
   174          char *uuid, *code, *dict, *url, *urlcode, *template, *p;
   175          char *src_name, *src_vers, *platform, *chassis, *server;
   176          char *typ, *sev, *fmt, *trfmt, *rsp, *imp, *act, *locdir;
   177          char msg[1024], desc[1024], date[64];
                ~~~~~~~~~~~~~~

   ....

   327          syslog_emit(hdl, msg, sizeof (msg),
   328              template, code, dgettext(dict, typ),
   329              dgettext(dict, sev), date, platform, chassis, server,
src_name,
   330              src_vers, uuid, desc, dgettext(dict, rsp),
dgettext(dict, imp),
   331              dgettext(dict, act));
                    ~~~~~~~~~~~~~~~~~~~~==> it is for REC-ACTION
*** (#1 of 1): 2008-03-21 01:18:28 CST  xxxxx@xxxxx.com
Work Around
Use the <EVENT-ID> from what is displayed to get the full message output via fmadm, e.g.

# fmadm faulty -u ad7ded7b-7062-4c92-8efe-323a6079b4cf
Comments
N/A