Sun Fire 12K/15K Domains with MaxCPUs in Split Expanders May "Dstop" with an "Undefined TTransID (UTT)"



Category :Availability
Release Phase :Resolved
Product :Sun Fire 12K Server
Sun Fire 15K Server  
Bug Id :4826949  
Date of Workaround Release :25-MAR-2003 
Date of Resolved Release :02-Apr-2008 

Under heavy load, Sun Fire 12K and 15K Domains with MaxCPUs in split expanders ... see below:


1. Impact

Under heavy load, Sun Fire 12K and 15K Domains with MaxCPUs in split expanders may "Dstop" with a processor asserting "Undefined TTransID (UTT)".


2. Contributing Factors

This issue can occur in the following releases:

SPARC Platform

  • Sun Fire 12K/15K with System Management Software (SMS) 1.1
  • Sun Fire 12K/15K with System Management Software (SMS) 1.2
  • Sun Fire 12K/15K with System Management Software (SMS) 1.3

Notes: To identify MaxCPUs in split expanders do the following:

	% showboards
	Location  Pwr  Type of Board   Board Status  Test Status  Domain
	--------  ---  -------------   ------------  -----------  ------
	SB12      On   CPU             Available     Unknown      A
	IO12      On   MCPU            Available     Unknown      B

IO12 is a MaxCPU board. Note that SB12 is assigned to Domain A and IO12 is assigned to Domain B. This indicates a split expander configuration involving a MaxCPU.

Also note that a MaxCPU in an expander that does not have a CPU board is NOT at risk. For example:

	% showboards
	Location  Pwr  Type of Board   Board Status  Test Status  Domain
	--------  ---  -------------   ------------  -----------  ------
	SB17	  -    Empty Slot      Available     -      	  Isolated
	IO17	  On   MCPU

The MaxCPU in IO17 is NOT in a split expander because SB17 is not physically present in the system.


3. Symptoms

A "Dstop" occurs when the hardware detects an unrecoverable error. This prevents further corruption of data and facilitates debugging.

The following would be recorded in the "Dstop" dump file. A message in the platform message log ("/var/opt/SUNWSMS/adm/platform/messages" file) would report:

	Feb 17 20:25:55 2002 swmtft901 hwad[22514]: [1156 1693005732870614 ERR 
	InterruptHandler.cc 2127] Domain Stop interrupt detected, domain XXX

SMS then creates a "Dstop" dump file in "/var/opt/SUNWSMS/adm/[XXX]/dump". The file name is "dsmd.dstop.YYMMDD.hhmm.ss" (year, month, day.hour_minute.seconds) For this example, if this dump file is opened with the "redx" command and the "wfail" command is issued, the output below is reported:

	sc% redx -cl
	redx> dumpf load dsmd.dstop.020117.2025.55)
	redx> wfail                 
	redxl> wfail
	SDI EX07/S0  Master_Stop_Status0[31:0] = 8000004A
        MStop0[3,1]: Slot 0 port is DStopped, SDI is Recordstopped.
	SDI EX07/S0  Dstop0[31:0] = 10029000
	Dstop0[17]: D    DARB texp requests Slot0 Dstop (M)
	Dstop0[28]: D 1E Slot0 asserted Error, enabled to cause 
	Dstop (M)
	EPLD SB07  Err1_Dom0: Mask= 00  Err= C1  1stErr= 40
	Err1[0]:      Error reported by AR
	Err1[6]:  1E+ Error reported by BBC0
	Err1[7]:      Error reported by BBC1
	BBC SB07/BB0   Device_Err_Stat[31:0] = 80008200
	DevErr[    9]:   1E  Port 1 Safari device asserted error
	Proc SB7/P1 (7.0.1) EmuShad[0:78] = 0008 00000000 00000000   
	(Note rev order)
	EmuSh[11]: UTT: TTransID in doesn't match any outstanding ATransID.
	AFSR [63:0] = 00081000.00000000   AFAR [42:4] = 007.F2ACA48_
	AFSR2[63:0] = 00080000.00000000   AFAR2[42:4] = 000.0000000_
	AFSR[44]:    TO: Unmapped error from system bus.
	AFSR[51]: 1E PERR: System interface protocol error.

4. Workaround

To work around the described issue, avoid configurations with MaxCPUs in split expanders.


5. Resolution
There are no further updates planned for this Sun Alert document. If
you need additional assistance regarding this issue, please contact Sun
Services.

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


Modification History

02-Apr-2008: no further updates. Resolved.




Attachments
This solution has no attachment

 
 
Login Required

You must login and have a valid contract to access Sun's Premium content which includes:

  • Sun Alerts
  • Bugs
  • Patches
  • Solutions
  • White Papers
  • Documentation
  • Support Knowledge

Login Required

You must login and have a valid contract to access Sun's contracted features

Access Legend:

(Login to access)   Sun Contracted Content
(Login to access)   Sun Contracted Feature

Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.

Search

Article Details
Article ID : 200584
Article Type : Sun Alert
Last reviewed : 2008-04-02
Audience : PUBLIC
Keywords :
Provide feedback  (help)
Page Tools
»  Print This Page
»  Email This Article
»  Bookmark This Article
 
Contact About Sun News & Events Employment Site Map Privacy Terms of Use Trademarks Copyright Sun Microsystems, Inc. | SunSolve Version 7.4.0 #1