Description

On SPARC M10-1, M10-4 and M10-4S Servers with XCP Firmware versions less than XCP2320, the system may panic after 1101 days of uptime.

Occurrence

This issue can occur on the following platforms:

SPARC Platform

• M10-1 Servers with XCP Firmware version less than XCP2320
• M10-4 Servers with XCP Firmware version less than XCP2320
• M10-4S Servers with XCP Firmware version less than XCP2320

and where Hypervisor was last loaded 1101 days ago on the system.

Notes:

1. The "showlogs event" output may return sufficient history to check the Hypervisor uptime. (Look for the line: "Start Hypervisor").

Example "showlogs event" output:

      ...
      Mar 23 13:42:15 SGT 2018 Current PPARs' phase (PPARID 0 POST phase: Start Hypervisor)
      Mar 18 13:06:02 SGT 2015 Current PPARs' phase (PPARID 0 POST phase: Start Hypervisor)
      Dec 15 10:49:30 SGT 2014 Current PPARs' phase (PPARID 0 POST phase: Start Hypervisor)
      ...

2. The Solaris GNU 'date' command can be used to easily calculate a date 1101 days earlier from the panic date, as in the following example:

      % /usr/gnu/bin/date -d "Jun 04 2017 - 1101 days"
      Friday, May 30, 2014 12:00:00 AM UTC

3. To find the current XCP version use one of these options:

    - On a live system issue "version -c xcp" from the XSCFU.
    - Or, from an Explorer output, the XCP version cn be found towards the bottom of the output from 'prtdiag-v.out'.
    - Or, in a snapshot the information can be found in the "@sp@cli@usr@bin@version_-c_xcp_-v.out" file.

      XSCF> version -c xcp
      BB#00-XSCF#0 (Master)
      XCP0 (Current): 2320
      XCP1 (Reserve): 2320

Example prtdiag output:
      .....
      ============================ FW Version ============================
      Version
      ------------------------------------------------------------
      2322

      ====================== System PROM revisions =======================

Example snapshot "@sp@cli@usr@bin@version_-c_xcp_-v.out"     

      BB#00-XSCF#0 (Master)
      XCP0 (Current): 2320
      ......

Symptoms

If this issue occurs, output from the uptime command will show 1101 days or more.

Example:

      12:46pm up 1101 day(s), 18:48, 12 user, load average: 2.68, 2.89, 2.85

A system may panic with a stack similar to the following:

      Dec 10 20:33:19 hostname ^Mpanic[cpu250]/thread=2a100017c80:
      Dec 10 20:33:19 hostname unix: [ID 152620 kern.notice] send_mondo_set: timeout
      Dec 10 20:33:19 hostname unix: [ID 100000 kern.notice]
      Dec 10 20:33:19 hostname genunix: [ID 723222 kern.notice] 000002a100017020 unix:send_mondo_set+548 (2, ffff, 1864860, 1, 3003f61e600, 1)
      Dec 10 20:33:19 hostname genunix: [ID 179002 kern.notice] %l0-3: 00000000000000fe 0151f4f547c9bdea 00000000010c5c00 00000000010c5c00
      Dec 10 20:33:19 hostname %l4-7: 0000000000000001 00000000010c5c90 0000000000000000 0000000000000001
      Dec 10 20:33:19 hostname genunix: [ID 723222 kern.notice] 000002a100017110 unix:xc_all+55c (10699b0, 0, fffffffffffffff8, 1915800, 199c710, 2a100017348)
      Dec 10 20:33:19 hostname genunix: [ID 179002 kern.notice] %l0-3: 0000000000000003 00000000018838a8 0000000001883818 0000000001883810
      Dec 10 20:33:19 hostname %l4-7: 00000000000000ff 0000000001883820 ffffffffffffffff 000002a1000178c0
      Dec 10 20:33:19 hostname genunix: [ID 723222 kern.notice] 000002a1000179c0 genunix:thread_reaper+14c (0, 1a6fc00, 1a7b000, 1a4d884, 2a100017a8a, 2a100017a88)
      Dec 10 20:33:19 hostname genunix: [ID 179002 kern.notice] %l0-3: 00000301d41578a0 0000030596bfed80 0000000001a7b000 0000000000000000
      Dec 10 20:33:19 hostname %l4-7: 0000000001a23000 0000000001a23000 0000000001a7b000 0000000001a6fc00
      Dec 10 20:33:19 hostname unix: [ID 100000 kern.notice]

Workaround

There is no Workaround for this issue. Please see the Resolution section below.

Resolution

This issue is addressed in the following releases:

SPARC Platform

• M10-1 - XCP Firmware version 2340 (as delivered in patch 26175660) or later
• M10-4 - XCP Firmware version 2340 (as delivered in patch 26175665) or later
• M10-4S - XCP Firmware version 2340 (as delivered in patch 26175673) or later

See also: <Document:1554086.1> - "Fujitsu M10-1/M10-4/M10-4S XSCF Control Package (XCP) Firmware Image Software Version Matrix Information" for additional information.

Patches

<Patch:26175660>, <Patch:26175665>, <Patch:26175673>

History

08-Sep-2017: Document released, status is Resolved
27-Mar-2018: Clarification to Note 1 in "Occurrence"

Questions regarding any portion of this document must be submitted to
sunalertpublication_us_grp@oracle.com and copy the
submitter/responsible engineer listed below.

Internal Contributor/Submitter: mike.cootware@oracle.com
Internal Eng Responsible Engineer: mike.cootware@oracle.com
Oracle Knowledge Analyst: david.mariotto@oracle.com
Internal Eng Business Unit Group: SPARC
Internal Associated SRs: 3-13297942191, 3-13633742252, 3-13635139075, 3-13792054041, 3-13795539135, 3-13837703051, 3-13889859911,
3-13938172976, 3-14018111568, 3-14019933801, 3-14098739671, 3-14107000511, 3-14173363937, 3-14212016146, 3-14256270241, 3-14278149109,
3-14316936811, 3-14329129391, 3-14331785001, 3-14336778381, 3-14372172561, 3-14444634911, 3-14444634931, 3-14444895384, 3-14467233301,
3-14467996461, 3-14468375331, 3-14476244231, 3-14490015221, 3-14525675121, 3-14531973051, 3-14544733891, 3-14643656517, 3-14661301441,
3-14661491441, 3-14663473191, 3-14723624411, 3-14758866621, 3-14848256161, 3-14938819291, 3-14952373141, 3-14953038947, 3-15041650021,
3-15158826216, 3-15247194961, 3-15248001994, 3-15403960101, 3-15470090921, 3-15479319605, 3-15551775511, 3-15558779011, 3-15559121601,
3-15578450201, 3-15633092363
Internal Resolution Patches: 26175660, 26175665, 26175673

References

This solution has no attachment