Skip to main content

Problems Resolved in XCP 3053


Problems Resolved in XCP 3053
The following table lists the problems resolved in XCP 3053.
Table 3-13  Problems Resolved in XCP 3053
RTI No. RTIF2-180926-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description An application may dump core because of misaligned data access, even if it is compiled by Oracle Developer Studio (Oracle Solaris Studio) with the -m64 option and any of the following options specified:
-xmemalign=2i

-xmemalign=4i

-xmemalign=8i

-xmemalign=16i

 
Details regarding the Oracle Solaris and compiler versions are as follows:
 
[Oracle Solaris 10 environment]
- All versions of Oracle Solaris 10

- All versions of Oracle Developer Studio (Oracle Solaris Studio)

 
[Oracle Solaris 11 environment]
- Oracle Solaris 11.1 or later

- Oracle Solaris Studio 12.3 or earlier

   (except Oracle Developer Studio 12.3 1/13 Platform Specific Enhancements)
 
[How to check the compiler version]
The -V option shows version information. The date is output at the end of version notation. The compiler version that causes this bug is 2013/10/18 or older.
 
cc -V
cc: Sun C 5.12 SunOS_sparc Patch 148917-07 2013/10/18
Workaround There is no effective workaround.
RTI No. RTIF2-180914-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description In a system with sixteen (maximum) 8 GB DIMMs mounted in the MBU (SPARC M12-1) or the CMUL or CMUU (SPARC M12-2/SPARC M12-2S), the following error may be wrongly detected when the physical partition (PPAR) is powered off. Then, the PPAR cannot be powered on. This symptom occurs when 8 GB DIMMs have been added or moved to the system.
 
 [Example 1] MBU (SPARC M12-1) error log
  XSCF> showlogs error -v
  Date: Sep 03 16:16:45 JST 2018
      Code: 40002008-001b110000ff0000ff-018f00010000000000000000
      Status: Warning                Occurred: Sep 03 16:16:43.153 JST 2018
      FRU: /MBU
      Msg: Power-off failure
      Diagnostic Code:
          00020000 00000000 0000
          00000000 00000000 0000
          00000000 00000000 0000
          00000909 4d801048 00000010 00000015
          00000000 00000000 0000
- You can confirm that the 5th and 6th bytes from the beginning of [Code:] are 001b and the 2nd byte on the first line of [Diagnostic Code:] is 02.

 
[Example 2] CMUL (SPARC M12-2/SPARC M12-2S) error log
  XSCF> showlogs error -v
  Date : Sep 03 15:09:56 JST 2018
     Code: 40002008-0052220000ff0000ff-018f00010000000000000000
     Status: Warning                Occurred: Aug 17 15:09:52.363 JST 2018
     FRU: /BB#0/CMUL
     Msg: Power-off failure
     Diagnostic Code:
         00000000 00000000 0000
         00000000 00000000 0000
         00000000 00000000 0000
         00000676 4df01608 00000010 00000025
         00000000 00000000 0000
- You can confirm that the 5th and 6th bytes from the beginning of [Code:] are 0052 and the 3rd byte on the first line of [Diagnostic Code:] is 00.

 
[Example 3] CMUU (SPARC M12-2/SPARC M12-2S) error log
  XSCF> showlogs error -v
  Date: Sep 03 15:09:56 JST 2018
     Code: 40002008-0070220000ff0000ff-018f00010000000000000000
     Status: Warning                Occurred: Aug 17 15:09:52.540 JST 2018
     FRU: /BB#0/CMUU
     Msg: Power-off failure
     Diagnostic Code:
         00000000 00000000 0000
         00000000 00000000 0000
         00000000 00000000 0000
         00000666 10001b10 00000010 00000025
         00000000 00000000 0000
- You can confirm that the 5th and 6th bytes from the beginning of [Code:] are 0070 and the 3rd byte on the first line of [Diagnostic Code:] is 00.


[How to restore]
Turn off the input power, and then turn it on again. (AC OFF/ON)
Workaround There is no effective workaround.