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-1587590.1
Update Date:2018-03-01
Keywords:

Solution Type  Problem Resolution Sure

Solution  1587590.1 :   Fujitsu M10-1/M10-4/M10-4S Servers: CPU Panic On Server Build  


Related Items
  • Fujitsu M10-4S
  •  
  • Fujitsu M10-4
  •  
  • Fujitsu M10-1
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Fujitsu M10
  •  
  • _Old GCS Categories>AIA>AIAReleases>Communications>Known Issues/Workarounds
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-7856034251>

Applies to:

Fujitsu M10-4S - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-1 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4 - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)

Symptoms

 System panics upon installing from Jumpstart or AI with panic stack:

{0} ok boot net - install
Boot device: /pci@8000/pci@4/pci@0/pci@1/network@0 File and args: - install
100 Mbps half duplex Link up
Requesting Internet Address for b0:99:28:98:68:0
100 Mbps half duplex Link up
SunOS Release 5.10 Version Generic_137137-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
-
panic[cpu0]/thread=180e000: assertion failed: add_ivintr(f_p->px_fh_sysino, PX_ERR_PIL, (intrfunc)f_p->px_err_func, (caddr_t)f_p, NULL, (caddr_t)&f_p->px_intr_payload[0]) == DDI_SUCCESS, file: ../../sun4v/io/px/px_lib4v.c, line: 1792

Changes

 

Cause

From the messages above "SunOS Release 5.10 Version Generic_137137-09 64-bit" shows that this version of Solaris does not support the M10-x platform.

Refer to Fujitsu M10 Product Notes ( linked from http://docs.oracle.com/cd/E38160_01 Chapter 1 page 1 ).

Minimum required version of Solaris 10 is:

Oracle Solaris 10 1/13 Update 11 

Solution

The jumpstart server may have been setup using a Solaris 10 Update 6 image, so the miniroot used for the jumpstart is also from Update 6. 

It may be pointed at the proper Solaris 10 Update 11 image, but  the device tree is generated by the miniroot, which doesn't have the proper drivers to handle the hardware.

Delete the jumpstart client from the existing jumpstart server and recreate it from an Update 11 image.

References

<NOTE:1002239.1> - How to Determine the Release and Default Kernel Version in the Solaris Operating System

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