Sun Fire[TM] 12K/15K/20K/25K: POST: memory crunched (c), be aware of possible missing (m) processors

Asset ID:	1-72-1589664.1
Update Date:	2018-05-09
Keywords:

Solution Type Problem Resolution Sure

Solution 1589664.1 : Sun Fire[TM] 12K/15K/20K/25K: POST: memory crunched (c), be aware of possible missing (m) processors

Applies to:

Sun Fire E20K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire E25K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire 12K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire 15K Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

When performing an hpost for a single System Board or even a complete domain for testing purposes
the result might end with crunched components. This document is focused on crunched memory.

See the following example that is focused to the end of an hpost for a single System Board SB08
in test domain R

   $ cat $SMSLOGGER/R/<logfile>
   # Sun Fire 12/15/20/25K POST log opened Thu Jul 19 01:25:46 2012
   # hpost version   1.6 SMS Development May 24 2010 01:05:06
   [...]
   Skipping OBP handoff as requested

   Key to resource status value codes:
   ?=Unknown       p=Present       c=Crunched      _=Undefined     m=Missing
   i=Misconfig     o=FailedOBP     f=Failed        b=Blacklisted   r=Redlisted
   x=NotInDomain   u=G,unconfig    P=Passed        ==G,lockstep    l=NoLicense
   e=EmptyCasstt

   CPU_Brds: Proc Mem P/B: 3/1 3/0 2/1 2/0 1/1 1/0 0/1 0/0
   Slot Gen 3210        /L: 10 10   10 10   10 10   10 10     CDC
   SB08: P   PPmm            PP mm   PP mm   cc cc   cc cc      P

   Exitcode = 36: Non-configuration special hpost mode successful
   POST (level=64, verbose=20) execution time 18:57
   # Sun Fire 12/15/20/25K POST log closed Thu Jul 19 01:44:42 2012

Changes

Cause

In general the status c=Crunched is an operation internal to POST that infers what components
are effectively unuseable (in one or more of the bus configurations) because other components
have failed, are missing, blacklisted or are otherwise unusable.

Please be aware that c=Crunched memory is not always related to f=Failed or otherwise
problematical components. For the example here the c=Crunched memory is simply due to the
fact that SB08 has no Processors 0 and 1 assembled. SB08/P0 and SB08/P1 are shown m=Missing.

Solution

To evaluate/confirm whether there is a real memory-related issue please take the actual
hardware configuration/population into account. Crunched memory might be simply related to
missing Processors. In this case the complete log of hpost clarifies that there is not any
CHS report or any blacklist entry or any FAIL for any component.

Additional Information
For detailed instruction on how to test a single System Board please refer to:
Sun Fire[TM] 12K/15K/E20K/E25K: Testing a single slot 0 board when no slot 1 board is present in domain and/or when slot 0 board is COD (Doc ID 1007568.1)

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate
My Oracle Support Community - Oracle Sun Technologies Community.

Attachments

This solution has no attachment