Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1587019.1
Update Date:2017-11-29
Keywords:

Solution Type  Problem Resolution Sure

Solution  1587019.1 :   M4000/M5000 Fails to boot after CPU upgrade  


Related Items
  • Sun SPARC Enterprise M4000 Server
  •  
  • Sun SPARC Enterprise M5000 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx000
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-7851652731>

Applies to:

Sun SPARC Enterprise M4000 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise M5000 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

M4000 fails to boot with the following message:

{0} ok boot rootdisk
Boot device: rootdisk File and args:
krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase



The same error is reported when booting from DVD

{0} ok boot cdrom
Boot device: /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@3,0:f File and args:
krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase

 

The XCP version is 1100

The OS on the boot disk and DVD is s10u10

The XCP and OS are compatible with the new installed CPUs according to Doc ID 1145383.1

Changes

M4000 was recently upgraded:
from
1 x CPUM SPARC VII 2.53GHz
2 x MEMB 8 DIMMs x 2GB
XCP version 1100

to
2 x CPUM SPARC VII+ 2.66GHz
2 x MEMB 8 DIMM x 4GB
XCP version 1100 

Cause

Firmware mis-match between XSCFU and MBU

The XSCFU had recently been replaced.
This can be confirmed by the outputs of "showlogs monitor" and "showlogs event"
The first recorded date is Jan 01 00:05:59 UTC 2001 the next date reported is the current date.

The replacement XSCFU had XCP version 1100 installed.
This is confirmed by running "version -c xscf-v"

XSCF#0 (Active )
01.10.0000(Current) 01.10.0000(Reserve)

XCP version 01.10.0000 equates to XCP version 1100


However the firmware on the MBU did not match that of the XSCFU
This can be confirmed by running " version -c cmu -v"

DomainID  0: 02.13.0000
DomainID  1: 02.13.0000
XSB#00-0:  02.13.0000(Current)     00.00.0000(Reserve)
XSB#00-1:  02.13.0000(Current)     00.00.0000(Reserve)
XSB#00-2:  02.13.0000(Current)     00.00.0000(Reserve)
XSB#00-3:  02.13.0000(Current)     00.00.0000(Reserve)

It can be seen from the above output that the firmware is at a different revision.
02.13.0000 equates to XCP version 1091

XCP version 1091 is not compatible with the new installed CPUs

 

The console logs indicate the attempts to boot and reports the following line during a boot attempt:
Sep 24 04:24:41 UTC 2013      OpenBoot 4.24.12, 65536 MB memory installed, Serial #91127684.

OpenBoot 4.24.12 also equates to XCP version 1091 further supporting the conclusion that there is a firmware discrepancy between the XSCFU and the MBU

Solution

 The solution is run flashupdate to upgrade the MBU to the same version as the XSCFU to enable the M4000 domain to boot.

The recommendation is to upgrade the XCP to the latest available.
Refer to : Sun SPARC[TM] Enterprise M3000, M4000, M5000, M8000, M9000 XSCF Control Package (XCP) Firmware Image Software Version Matrix Information (Doc ID 1002631.1)

References

<NOTE:1145383.1> - SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Server Matrix for Hardware, Firmware and Software
<NOTE:1002631.1> - Sun SPARC[TM] Enterprise M3000, M4000, M5000, M8000, M9000 XSCF Control Package (XCP) Firmware Image Software Version Matrix Information

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback